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: 160
Popularity: 0.019293
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 .. 73 74 75 76 77 78 79 80 81 82 83 .. 152 Next › Last »

juston_li commented on 2013-06-08 04:58 (UTC)

Failed to open Chormium after upgrading harfbuzz too. /usr/lib/chromium-dev/chromium: symbol lookup error: /usr/lib/chromium-dev/chromium: undefined symbol: hb_icu_get_unicode_funcs Downgraded harfbuzz

xavier114fch commented on 2013-06-08 03:47 (UTC)

Fail to build after harfbuzz upgrade. extra/harfbuzz 0.9.18-1 [installed] OpenType text shaping engine http://pastie.org/8021767

sl1pkn07 commented on 2013-06-07 11:46 (UTC)

no sources = no party :(

misc commented on 2013-06-06 20:38 (UTC)

Crash reporting is not available for Chromium. From their FAQ page: > Chrome handles its own crashes by linking in Breakpad, whereas Chromium does not link in Breakpad. Therefore, when a Chromium crash occurs, it is simply ignored. You can still get a classic trace, see the ArchWiki "Debug - Getting Traces" for that. (Warning — I did that one, the compilation took ages and the package grew to little less than 900 MiB.)

juston_li commented on 2013-05-30 14:17 (UTC)

Perhaps a dumb question but is crash reporting disabled? I can't seem to find a way to retrieve crash ID. Say's "Crash reporting is disabled. Crash reporting is not available in Chromium." And the report crash statistics is not in settings. Thanks for the packages by the way

sl1pkn07 commented on 2013-05-10 01:02 (UTC)

update to 28.0.1500.5 - toolchain_linux -> no need anymore, thanks @misc for the tip note for: * Instead of patching libvpx, adding "-Dlibvpx_source=/usr/include" to _flags does the same. I prefer patch, and none of the two ways is necessary en next version https://code.google.com/p/chromium/issues/detail?id=226860#c18 greetings

misc commented on 2013-05-09 18:01 (UTC)

Two notes: * toolchain_linux_x86.tar.bz2 isn't necessary, at least I've never downloaded it. * Instead of patching libvpx, adding "-Dlibvpx_source=/usr/include" to _flags does the same.

sl1pkn07 commented on 2013-05-08 23:12 (UTC)

update to 28.0.1500.3 - add initial support to unit test (disable for default, need huge test (for me get out of memory (?¿)) - add some patch from gentoo build - add part of code from @misc pkgbuild (pnacl related) (tnx bro) - back need lib32-gcc-libsa and lib32-zlib. need active multilib repository in pacman.conf (finaly make more test (without trolling me) with chrooted installation, yes, only need these two packages, no need more.) and add warning message if detect x64 systems - now use own v8 packgae called v8-dev, this package is updated when released dev channel thanks all for the patient greetings and enjoy! http://www.youtube.com/watch?v=EsMNqUVv3mQ

« First ‹ Previous 1 .. 73 74 75 76 77 78 79 80 81 82 83 .. 152 Next › Last »