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.
Search Criteria
Package Details: google-chrome 131.0.6778.85-1
Package Actions
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.18 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-19 19:19 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet (kwallet-gitAUR) (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (40)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-extension-adnauseam (optional)
- chromium-extension-autoscroll (optional)
- chromium-extension-plasma-integration (optional)
- chromium-extension-runet-censorship-bypass (optional)
- chromium-material-icons-for-github-bin (optional)
- chromium-vencord (optional)
- chromium-vencord-bin (optional)
- chromium-vencord-git (optional)
- dedao-dl-bin (optional)
- endpoint-verification-chrome
- endpoint-verification-minimal
- ff2mpv-go-git (optional)
- ff2mpv-rust (optional)
- hub-kids (optional)
- hub-young (optional)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 157 Next › Last »
PeterRies commented on 2023-05-04 07:37 (UTC)
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)
gromit commented on 2023-05-03 07:42 (UTC)
@Kandscode did you put custom flags in "~/.config/chrome-flags.conf" by any chance? In any case you could start chrome from a terminal and see if an error pops up :)
Kandscode commented on 2023-05-03 04:46 (UTC)
Chrome version 113.0.5672.63-1 does not start on my computer for unknown reasons.
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:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.