Package Details: google-chrome 130.0.6723.116-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: 2243
Popularity: 7.00
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-05 19:02 (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 »

Xavion commented on 2017-02-03 19:44 (UTC)

A tiny bit of housekeeping: you've got an extra colon after 'kdialog' in the PKGBUILD (making it "kdialog::"). This prevents 'pacman' from displaying '[installed]' after it. I just went and tried to install 'kdialog', not realising I didn't need to.

Det commented on 2017-01-24 14:40 (UTC) (edited on 2017-01-24 14:40 (UTC) by Det)

> wiyarmir [1] added the following comment to google-chrome [2]: > > The build script complained about fakeroot command being missing although not being stated as a dependency (PKGBUILD) See: https://wiki.archlinux.org/index.php/Arch_User_Repository#Getting_started

Det commented on 2017-01-23 18:18 (UTC)

> DeadMetaler flagged google-chrome out-of-date on 2017-01-23 for the following reason: > > https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-chrome-os.html That's Chrome OS.

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.

« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 157 Next › Last »