Package Details: google-chrome 129.0.6668.58-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2236
Popularity: 7.19
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (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 "Stable 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-stable" | \
     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 .. 60 61 62 63 64 65 66 67 68 69 70 .. 157 Next › Last »

fuan_k commented on 2017-01-20 17:29 (UTC)

Thanks Det. Found that 55.0.2873.0 (unstable channel) was the version that started breaking. I've updated my bug report. Looks like someone is on the case now.

Det commented on 2017-01-19 15:11 (UTC)

> rborja flagged google-chrome out-of-date on 2017-01-19 for the following reason: > > I get a 404 error when running wget command. It's not out-of-date..

Det commented on 2017-01-17 18:48 (UTC) (edited on 2017-01-17 18:49 (UTC) by Det)

For sure, but I was just trying to help in bisecting. It's much easier for the devs when you've narrowed down the exact build ("1.14.1 works, 1.14.2 is broken").

fuan_k commented on 2017-01-17 18:11 (UTC)

Thanks Det, but I suspect it's an issue in the chromium code base as the bug didn't occur in 53.0.2785.143, and it occurs in 55.0.2883.87 (as stated in the bug report). Hopefully they will notice it and fix it eventually.

Det commented on 2017-01-15 17:46 (UTC)

By the way, you said "Did this work before? Yes 54. probably? Can't remember." in your report. You can find those older ones stacked in here: http://mirror.glendaleacademy.org/chrome/pool/main/g/google-chrome-stable/ (link in google-chrome-dev PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome-dev#n31)

fuan_k commented on 2017-01-09 12:43 (UTC)

@mikioma totally unrelated, tested on different machines with different hardware (nvidia and amd). See bug report link for details. It's a regression in Chromium 55. Could be a library issue, or just the chromium code itself.

mikioma commented on 2017-01-09 08:39 (UTC)

@fuan_k If you happen to own an AMD/ATI card and Chrome's freeze status reverts by switching to a VT and swithing back to graphic desktop, then you're on the same page than other distros (Fedora among others). Seems to be related to graphics driver and get solved by launching Chrome with --disable-gpu flag... that makes it unusable, though (slow as pain...)

fuan_k commented on 2017-01-06 17:44 (UTC)

Can anyone reproduce the following bug (it will hang Chrome/Chromium) 1) set "Ask where to save each file before downloading" in settings 2) open TWO tabs in which downloads will start after a short countdown (for example: https://sourceforge.net/projects/pipestatus/files/pipestatus/pipestatus-0.6.0/pipestatus-0.6.0.tar.gz/download). This works with any website, including video or image files when using "save as" very quickly in a row several times. 3) wait for the TWO GtkFileChooserDialog windows to open 4) click "cancel" in the top most "Save file as" dialog window (saving yields the same results in the end) 5) in the second (remaining) opened dialog, cancel as well (or save, same result next step anyway) 6) Chrome will start downloading the file if you chose to, but the user inputs are not registered anymore (mouse and keyboard alike). You will have to kill Chrome afterwards. I have submitted a bug report to Chromium bugtracker: https://bugs.chromium.org/p/chromium/issues/detail?id=678982

Det commented on 2016-12-29 17:45 (UTC) (edited on 2016-12-29 17:50 (UTC) by Det)

Stop sending you? :D I sent you _one_ _single_ email for the fact that you flagged this package twice because of your weird old build, when you can clearly see the package version up there is 55.0.2883.87. Any other emails would be due to the notifications *you* enabled. Btw. did you once 'ls' that directory or check the Wget output? I bet you get: $ ls google-chrome.tar.gz google-chrome.tar.gz.1 google-chrome.tar.gz.2 etc...

<deleted-account> commented on 2016-12-28 23:01 (UTC)

home from work. here is a screenshot of my bash history from yesterday. http://i.imgur.com/f6VdKhj.png you can see on entry 475 where i mashed tab for autocomplete. the other option was google-earth. i dunno what you want. i navigated to the aur package page, and i followed instructions about flagging the package when md5sums don't match. i appreciate the effort that you put into this and other packages. however, please stop sending me email.