Package Details: google-chrome 133.0.6943.53-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: 2261
Popularity: 11.00
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-02-05 10:39 (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 »

juangiordana commented on 2023-06-02 11:18 (UTC) (edited on 2023-06-02 11:39 (UTC) by juangiordana)

@gromit It works OK now.

Thanks for fixing it that quickly.

gromit commented on 2023-06-02 10:22 (UTC)

@juangiordana thanks for the suggestion, could you check that comments are respected with the latest version I just pushed?

I modified your diff a bit so that only lines are ignored where the # is at the start of the line :)

juangiordana commented on 2023-06-02 10:00 (UTC)

/usr/bin/google-chrome-stable does not strip commented lines as suggested in the Arch Wiki. https://wiki.archlinux.org/title/Chromium#Making_flags_persistent

-CHROME_USER_FLAGS="$(cat $XDG_CONFIG_HOME/chrome-flags.conf)"
+CHROME_USER_FLAGS="$(grep -v '#' $XDG_CONFIG_HOME/chrome-flags.conf)"

Ildar commented on 2023-05-24 07:43 (UTC) (edited on 2023-05-24 07:46 (UTC) by Ildar)

Here is my changes in ~/.config/chrome-flags.conf to get working GPU acceleration again
- --use-gl=egl
+ --enable-gpu
Source: https://bugs.chromium.org/p/chromium/issues/detail?id=1412653

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.

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