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 .. 24 25 26 27 28 29 30 31 32 33 34 .. 91 Next › Last »

xvoprsalek commented on 2014-02-26 14:16 (UTC)

Now the ' -> Compressing package...' takes several times longer.

Det commented on 2014-02-24 05:16 (UTC)

Removed "PKGEXT='.pkg.tar'" due to a request of having your own way through makepkg.conf.

phaseburn commented on 2014-02-23 23:24 (UTC)

I had the same issue as @wilberfan, with the renderer locking up constantly. I nuked my whole Chrome profile, didn't sign in upon opening Chrome, went to gmail.com and signed in there (so it wouldn't sync my profile back), and it locked up with just that tab open. Downgrading to 1838 resolved all issues of the renderer process crashing on gmail and other sites.

wilberfan commented on 2014-02-23 06:23 (UTC)

This build doesn't work well for me at all: repeated "Page(s) Unresponsive" errors. (Which is probably why I can't scroll any pages, either...)

Det commented on 2014-02-20 12:38 (UTC)

Those busy buggers.

<deleted-account> commented on 2014-02-20 12:20 (UTC)

According to http://googlechromereleases.blogspot.com.br/ there's a new Dev version available.

colinkeenan commented on 2014-02-19 17:42 (UTC)

Thanks for all your help, Det. I'm glad I asked. I followed your advice that you posted on my package's AUR page.

Det commented on 2014-02-19 14:21 (UTC)

Mm. The .deb you can extract with bsdtar (which is done automatically) and contains the following files (the data.tar.lzma is the only thing we care for): control.tar.gz (6,5 kB) data.tar.lzma (45,9 MB) debian-binary (4 B) It may also be something like .tar.gz or .tar.xz, but in Chrome's case it's a .lzma. Either way, this one you have to extract yourself (from the PKGBUILD): msg2 "Extracting the data.tar.lzma" bsdtar -xf data.tar.lzma -C "$pkgdir/" So it's not like makepkg only loves me, rather, it just does what I'm telling it to do.

colinkeenan commented on 2014-02-19 14:00 (UTC)

I have a question about the PKGBUILD because I've uploaded a couple of packages (nautilus-data and gnome-search-tool-no-nautilus) to AUR for the first time and am mystified by how you do "Extracting the data.tar.lzma" even though you downloaded a .deb file and never got data.tar.lzma out of it. My package nautilus-data also downloads a .deb file, but I had to use deb2targz available in the AUR in order to use it.

<deleted-account> commented on 2014-02-14 02:15 (UTC)

34.0.1838.2 released.