Package Details: google-chrome-dev 132.0.6793.2-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: 653
Popularity: 1.32
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-10-24 21:01 (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 .. 3 4 5 6 7 8 9 10 11 12 13 .. 91 Next › Last »

Det commented on 2016-08-12 18:28 (UTC)

Done, I hope you're right.

alumni commented on 2016-08-12 18:26 (UTC)

StartupWMClass has changed again. First letter should be capitalized: Google-chrome-unstable

Det commented on 2016-08-03 10:38 (UTC)

Canary? It's not for Linux.

hendry commented on 2016-08-03 10:29 (UTC)

Anyone else finding canary really really slow today?

Det commented on 2016-06-30 14:37 (UTC)

Don't post a comment about it, flag the package.

KSarv commented on 2016-06-30 05:51 (UTC)

>> checksum >What about it? Because it's totally up-to-date. Can't build it too because of checksums

Det commented on 2016-03-25 21:49 (UTC)

> Your package google-chrome-dev [1] has been flagged out-of-date by hexdsl [2]: > checksum What about it? Because it's totally up-to-date.

Det commented on 2016-03-09 05:02 (UTC) (edited on 2019-04-09 21:17 (UTC) by Det)

✔ NOTE. If the sha512sums don't match, there's a new version. Simply flag the package.

You can check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates, or use:

$ curl -sL https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'

For new MD5: $ curl -sL https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | sed -n '54p'

Det commented on 2016-02-10 07:03 (UTC) (edited on 2016-02-10 07:08 (UTC) by Det)

*OBS!* 32-bit support for Google Chrome Dev Channel has been dropped. Either upgrade to 64-bit, or stick to [extra]/chromium, which will continue to be updated: - http://linux.slashdot.org/story/15/12/01/1524259/google-to-drop-chrome-support-for-32-bit-linux

Det commented on 2016-02-04 09:35 (UTC) (edited on 2016-02-04 10:38 (UTC) by Det)

I haven't had that in a long time, if you mean the one where I think all 4 components, Nvidia/Xorg/KDE/Chrome were involved. E: Might have also been caused by no longer force-enabling GPU acceleration in chrome://flags/: - https://bbs.archlinux.org/viewtopic.php?id=198817 - http://linux.slashdot.org/story/14/03/04/1926233/google-wont-enable-chrome-video-acceleration-because-of-linux-gpu-bugs - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1466670

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 91 Next › Last »