Package Details: google-chrome 131.0.6778.85-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: 2247
Popularity: 9.36
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-19 19:19 (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 .. 22 23 24 25 26 27 28 29 30 31 32 .. 157 Next › Last »

nallekarhu commented on 2021-07-22 01:53 (UTC)

@koshikas Yeah, I'm not surprised, after all this is not your normal run of the mill git package.

FWIW, I have no problems with "google-chrome 92.0.4515.107-1" and systemd 249 after disabling systemd-resolved.

koshikas commented on 2021-07-22 01:07 (UTC)

the fix has been merged but will be only be available to the next build. they are not recalling the current build since, i quote;

"It seems Ubuntu is using systemd 247 in their most recent non-LTS and debian is using 247 in their testing branch. Fedora 34 is on 248 and probably won't be on 249 for a while. openSUSE tumbleweed isn't on it either. Those are our officially supported Linux distros. Definitely merge this to 93. But this is probably simple and safe enough to merge it to 92 given that it causes crashes for anyone using systemd 249."

source: https://bugs.chromium.org/p/chromium/issues/detail?id=1221442#c23 https://bugs.chromium.org/p/chromium/issues/detail?id=1221442#c21

nallekarhu commented on 2021-07-21 22:25 (UTC)

@bulletmark Hmm.. it looks to me that "chromium 92.0.4515.107-3" applies two fixes and removes the workaround in "chromium 92.0.4515.107-2", so it makes me think you don't need it.

bulletmark commented on 2021-07-21 21:59 (UTC)

@nallekarhyu, note that was the second commit applied to chromium. The first commit is required as well.

Tyrin.price commented on 2021-07-21 21:35 (UTC)

Now we just need an updated AUR package and we'll be set.

nallekarhu commented on 2021-07-21 18:44 (UTC)

Fixed on chromium side.. "chromium 92.0.4515.107-3: upstream fixes for glibc and systemd"

mappy24 commented on 2021-07-21 14:00 (UTC)

I'm not sure if this is related to the other issues being reported here, but after updating to 92.0.4515.107 this morning I find that I can no longer print as the print dialog completely crashes Chrome. Rolling back to 91.0.4472.164 has made printing work again.

When trying to print, the dialog appeared briefly with a spinning blue circle where the destination printer should have been before crashing. Running from the terminal shows this:

$ google-chrome-stable
[4616:4616:0721/144506.411907:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[4571:4571:0721/144511.137322:ERROR:print_preview_handler.cc(837)] Initiated PrintPreviewHandler::HandleGetInitialSettings()
[4571:4571:0721/144511.199407:ERROR:print_preview_handler.cc(529)] Initiated PrintPreviewHandler::HandleGetPrinters()
[4571:4571:0721/144511.216482:ERROR:print_preview_handler.cc(562)] Initiated PrintPreviewHandler::HandleGetPrinterCapabilities()
Segmentation fault (core dumped)

JoveYu commented on 2021-07-21 10:40 (UTC) (edited on 2021-07-21 10:40 (UTC) by JoveYu)

if you use yay, you can use package cache

cd ~/.cache/yay/google-chrome
yay -U google-chrome-91.0.4472.164-1-x86_64.pkg.tar.zst

benoliver999 commented on 2021-07-21 10:11 (UTC)

Same issue here, also fixed by downgrading chrome.

The 'download' button on the AUR commit history page is incredibly useful.

bulletmark commented on 2021-07-21 06:15 (UTC)

@b3nn, you mean version 248.3-2, and yes that does fix it. But I suggest it is much more sensible to simply downgrade google-chrome.

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 157 Next › Last »