Package Details: google-chrome 137.0.7151.55-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: 2280
Popularity: 11.69
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-05-27 18: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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 159 Next › Last »

gerald82 commented on 2023-05-05 08:52 (UTC)

With chrome >= 113 I get the same wayland issue as Iyanmv already reported. I wanted to add that while it does scale incorrectly in any case, using it with KDE Plasma is particularly bad when the system window borders are enabled, because then the window is also displayed incorrectly, e.g. you can't click a link that is too far on the right side.

However, a quick search implies that it is very unlikely that the issue is caused in packaging. More likely, it's a bug either in chrome or in plasma-wayland. And since I experience the issue only with chrome and no other application, I guess it's a chrome bug.

alki commented on 2023-05-05 02:06 (UTC)

Same issue as @kstolp and @PeterRies, and that flag works for me. From that forum linked, deleting the directory ~/.config/chromium/Default/GPUCache also resolved my issue.

kstolp commented on 2023-05-04 07:52 (UTC)

I experienced the same issues as @PeterRies. (Also AMD GPU with chrome hardware acceleration enabled.) Starting chrome with --disable-gpu-driver-bug-workarounds fixed it for me.

Fix found on forum here.

PeterRies commented on 2023-05-04 07:37 (UTC)

The upddate from May, 3rd in combination with a "complete systemupdate" on May, 4th broke display of (some) webpages. Fonts were missing. After some play around (-dev package works fine) I discovered that disabling GPU hardware acceleration in Settings/System solved the issue on my (AMD-Ryzen) Laptop.

Nanami commented on 2023-05-03 22:14 (UTC)

Seems like version 113 raises scaling issues on Wayland, XWayland still works though.

Kandscode commented on 2023-05-03 15:40 (UTC)

Oh, I used the flag --gtk-version=4, which causes Chrome to crash.

iyanmv commented on 2023-05-03 15:30 (UTC)

Anyone having issues with the latest version on Wayland? All app is wrongly scaled with --ozone-platform-hint=auto in ~/.config/chrome-flags.conf

Kandscode commented on 2023-05-03 15:22 (UTC)

@gromit Oh, I reinstalled Chrome after deleting all Chrome related files and now it's working fine again, sorry to bother.

gromit commented on 2023-05-03 14:55 (UTC)

@Kandscode you could try a few things:

  • see if the problem also exists for google-chrome-{beta,unstable} if you didnt specify any custom flags this might indicate there is a bug with chrome itself
  • create the path in the error message /home/kands/.config/google-chrome/Crash Reports/attachments/ and see if the error is then successfully written out there

Kandscode commented on 2023-05-03 14:47 (UTC)

@gromit When I start chrome in the terminal, the following error message will appear, and I have not used any flags.

$ google-chrome-stable 

[0503/224505.364103:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0503/224505.377502:ERROR:directory_reader_posix.cc(42)] opendir /home/kands/.config/google-chrome/Crash Reports/attachments/7ede611b-8e62-4d29-a7e2-0086571ee395: No such file or directory (2)
Segmentation fault (core dumped)

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 159 Next › Last »