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.15
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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 157 Next › Last »

god commented on 2023-05-17 01:53 (UTC)

As @Kandscode says, passing --gtk-version=4 crashes Chrome. Is there any workaround for that? Without that parameter, FCITX (input method editor) does not work and I cannot type CJK text.

iyanmv commented on 2023-05-09 09:11 (UTC)

One possible upstream report regarding scaling in Wayland: https://bugs.chromium.org/p/chromium/issues/detail?id=1430500

Raymo111 commented on 2023-05-05 21:58 (UTC)

I faced the same issue with almost no text rendering, @alki 's solution fixed it for me. Thanks alki!

P.S. this was a sign for me to switch to Vivaldi...

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.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 157 Next › Last »