Package Details: google-chrome-dev 133.0.6876.4-1

Git Clone URL: https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy)
Package Base: google-chrome-dev
Description: The popular web browser by Google (Dev Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 654
Popularity: 1.04
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-12-05 16:18 (UTC)

Dependencies (12)

Required by (41)

Sources (3)

Pinned Comments

gromit commented on 2023-07-19 17:01 (UTC) (edited on 2023-07-19 17:02 (UTC) by gromit)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Dev updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-unstable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 78 79 80 81 82 83 84 85 86 87 88 .. 91 Next › Last »

<deleted-account> commented on 2010-10-08 07:43 (UTC)

Probably a better solution would be to build a libpixbufloader-jpeg.so statically linked to libjpeg8. That way programs launched by Chrome (like when you download and run an executable) won't crash.

Det commented on 2010-10-07 22:48 (UTC)

Ah, of course. Since it's for libjpeg6 to which this whole thing is built for. I somehow got the idea that you just needed the file itself in that 'hack'.

OttoA commented on 2010-10-07 19:37 (UTC)

@Det thats the recent libpixbufloader-jpeg.so - for chrome to run properly you need an older one

Det commented on 2010-10-07 18:38 (UTC)

Hmm, good to know. But gdk-pixbuf2's ([testing]) libpixbufloader-jpeg.so isn't enough?

<deleted-account> commented on 2010-10-07 14:58 (UTC)

To fix the libjpeg6 related crash when posting JPEGs: 1. Obtain a libpixbufloader-jpeg.so that links to libjpeg6 (I stole mine from Ubuntu Karmic's GTK package) 2. Put it in /opt/google/chrome/ 3. Run: sudo gdk-pixbuf-query-loaders>/opt/google/chrome/loaders.cache 4. Open the loaders.cache and change the line referring to libpixbufloader-jpeg.so to point to the one you put in /opt/google/chrome/ 5. Open the google-chrome script and add somewhere before the exec: export GDK_PIXBUF_MODULE_FILE=/opt/google/chrome/loaders.cache I don't know how I would go about writing a patch or PKGBUILD that does this, but would it work? It works for me.

Det commented on 2010-10-06 14:47 (UTC)

See here: http://code.google.com/p/chromium/issues/detail?id=54932#c5

haagch commented on 2010-09-30 22:31 (UTC)

Are there any news about --enable-gpu-rendering? I have not seen it work on any of the following: intel 945gme with xf86-video-intel, radeon hd 4670 with either catalyst or xf86-video-ati-git...

<deleted-account> commented on 2010-09-30 09:30 (UTC)

update please

beej commented on 2010-09-29 01:07 (UTC)

It is a little funky to have the package version out of sync with the chrome version. I've been modding the PKGBUILD by hand when a new rev comes out. I certainly never minded the frequent updates to the package--it let me know when a new dev channel build was out. Just my $0.02.

Det commented on 2010-09-17 12:26 (UTC)

@Zom, if you want to do that with your package, I won't step in your way but I am not going to redownload a package that has specific release versioning again every time a new version comes up. You might as well not change the pkgrel at all, if you think your ideology is correct - which it is not.

« First ‹ Previous 1 .. 78 79 80 81 82 83 84 85 86 87 88 .. 91 Next › Last »