AUR (en) - chromium-dev

Search Criteria

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.010897
First Submitted:	2010-05-17 09:04 (UTC)
Last Updated:	2024-04-21 19:18 (UTC)

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.010897

First Submitted:

2010-05-17 09:04 (UTC)

Last Updated:

2024-04-21 19:18 (UTC)

Latest Comments

« First ‹ Previous 1 .. 93 94 95 96 97 98 99 100 101 102 103 .. 152 Next › Last »

sl1pkn07 commented on 2012-06-12 17:49 (UTC)

update to 21.0.1171.0 - remove disable_glibc (fail build) - set use_system-libvpx to 0 (if set 1 fail build) - add patch to fix memory_details_linux.cc build - remove patch chromium-expat-r0.patch - change patch gcc47v3.patch to gcc47v4.patch - remove patch ipc-fix.diff greetings

wuffleton commented on 2012-06-08 08:17 (UTC)

Looks like my ALSA issue was due to chromium not liking the IPC key I had set for dmixer. Changing it from 4096 to 3072 resolved the issue. I'm currently compiling 21.0.1167.0 to see if the fix has been merged yet. Besides a few of the patches becoming unnecessary or requiring edits, it would seem that disable_glibc needs to be set to 0 in order to compile. The bug that required it to be set to 1 appears to have been resolved, and if set to 1 now, the build will fail. (Just a heads up for any other people wanting try the bleeding-edge tarballs for bug fixes)

jeagoss commented on 2012-06-07 22:39 (UTC)

The extensions problem will be fixed in the next revision. http://src.chromium.org/viewvc/chrome?view=rev&revision=140954

wuffleton commented on 2012-06-05 18:24 (UTC)

Any other pure-ALSA users having issues with the new version and HTML5 Audio/Video? It floods messages similar to this on the command line when attempting to do anything that makes noise: [13373:13386:5014272109:ERROR:alsa_output.cc(670)] ALSA returned 4073 of 3763 frames available. [13373:13386:5014457904:ERROR:alsa_output.cc(670)] ALSA returned 4058 of 3763 frames available.

sl1pkn07 commented on 2012-06-03 17:07 (UTC)

no crash for me, but if left click in plugins don't show menu of these plugins

misc commented on 2012-06-03 11:37 (UTC)

Me too. Also, Chromium crashes if I try to deactivate such extensions (eg. ScriptNo) via right click menu.

jeagoss commented on 2012-06-03 01:12 (UTC)

I've noticed the same behavior as DarkSniper. Trying to step through it in gdb.

wuffleton commented on 2012-06-03 01:04 (UTC)

Anyone else having weird behavior with extension menus in this version? I've found that the menus for extensions like adblock and ghostery (which have toolbar buttons next to the wrench menu) appear on the wrong side of the window if at all.