Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 158
Popularity: 0.005234
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 102 103 104 105 106 107 108 109 110 111 112 .. 152 Next › Last »

<deleted-account> commented on 2012-04-25 16:15 (UTC)

Giant angry red bar at the top of the screen, lack of icons, and this error message: (chromium:1528): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. Feature? or bug? hahaha... Rebuilding now to see if this was just a bad build on my system, or if it's Chromium's fault. May wanna hold off on upgrading in the meantime.

yetAnotherZero commented on 2012-04-21 20:06 (UTC)

@DarkSniper Thanks for that. I recompiled it and it's awesome. I just did a pacman -Rdd gcc gcc-libs libtool lib32-gcc-libs then pacman -U on all those pkg versions you mentioned below. After the compile finished I did a pacman -Syu to get my system back up to par Thanks again

wuffleton commented on 2012-04-20 18:12 (UTC)

@speed: I compiled it in a chroot using GCC4.6 with the Clang option and the crashes are gone for me. People reported that it doesn't crash if compiled under GCC 4.6, but downgrading GCC on your working install could potentially cause catastrophic breakage. A chroot seems to be the best (and only) existing workaround at this point. I followed this guide for the chroot creation: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot (Beware: If you're using BTRFS, it makes a subvolume for the chroot, so you have to use btrfs sub delete if you wish to remove the chroot, as rm -rf won't work) Here's my package list for the chroot, which has everything you need to compile chromium (replace the base base-devel sudo part of the mkarchroot command with this): http://pastebin.com/vj6NL75r Get version 4.6.3-1 of core/gcc, core/gcc-libs, and multilib/lib32-gcc-libs (x86_64 only) and version 2.4.2-4 of core/libtool from http://schlunix.org/archlinux/ and install them into your chroot with "pacman -r /path/to/your/chroot/root -U <paths to downloaded packages here>" Before running mkchrootpkg, you'll probably need this edited PKGBUILD (It's up to you whether to use clang or not): http://pastebin.com/D7W50u6R The '"${srcdir}"/../' bits in package() don't work with mkchrootpkg because it doesn't store the source files one level above $srcdir. I've changed instances of this to '"${srcdir}"/', since install seems to treat the symlinks as normal files. I have not tested this yet (I copied the source files to $srcdir/../ manually), but it should work as intended. Hope this helps at least a few other users until the chromium team fixes GCC 4.7 support!

yetAnotherZero commented on 2012-04-20 17:21 (UTC)

Anyone have feedback regarding the omnibar crashes? It's a little sad everytime I forget and try to use it...

wuffleton commented on 2012-04-12 08:53 (UTC)

Using those options didn't seem to fix the segfault. After putting the omnibox through some abuse, it still crashes. I'm getting something slightly different on the command line now, though the dmesg output seems to be very similar if not identical to the previous segfault. From Command Line: [2695:2695:120527473823:ERROR:content_settings_pref_provider.cc(493)] Invalid pattern strings: ,* [2695:2695:120527475053:ERROR:content_settings_pref_provider.cc(363)] Invalid pattern strings: ,* [2695:2730:120535207943:ERROR:diagnostic_error_delegate.h(31)] sqlite error 11, errno 0: database disk image is malformed (This one doesn't always occur) Segmentation fault (core dumped) From dmesg: [120553.729454] Chrome_HistoryT[2730] general protection ip:7f1df11d6247 sp:7f1dd88722a0 error:0 in chromium[7f1defabb000+4524000]

sl1pkn07 commented on 2012-04-12 06:29 (UTC)

in my case. with ICU 4.9 from testing (with use_system_icu=1) Program received signal SIGSEGV, Segmentation fault. 0x00007ffff3f16354 in icu_49::RegexMatcher::reset(icu_49::UnicodeString const&) () from /usr/lib/libicui18n.so.49

wuffleton commented on 2012-04-12 05:54 (UTC)

@ sl1pkn07: Awesome! Compiling now to see if it fixes the issue.

sl1pkn07 commented on 2012-04-12 04:52 (UTC)

i think found problem described by @ DarkSniper (segfaults in omnibox) please test with: use_system_icu=0 and add "\! -path 'third_party/icu/*' \ in" in remove unnecesary components greetings

jeagoss commented on 2012-04-12 02:28 (UTC)

The patches still need testing to make sure I got everything. So please test away.

« First ‹ Previous 1 .. 102 103 104 105 106 107 108 109 110 111 112 .. 152 Next › Last »