Arch Linux User Repository

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.

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.

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.

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.

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

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

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

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

@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

@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)

@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 :)

Chrome version 113.0.5672.63-1 does not start on my computer for unknown reasons.

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.

On latest endeavouros install, this package isnt working properly, the windows is unreactive and cannot browse anything. After many attemps to solve this issue, luck helped a little. After installing brave from AUR, it seems it helped google-chrome to run.

here is the list of pacakges required by brave installation: [2023-02-06T22:30:18+0100] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- extra/rust community/cargo-audit extra/cbindgen extra/compiler-rt extra/clang community/cxxbridge extra/gn extra/gperf extra/java-runtime-common extra/libnet extra/jre-openjdk-headless community/oniguruma community/jq extra/lld extra/llvm community/ninja extra/c-ares community/nodejs community/nodejs-nopt community/semver community/node-gyp community/npm extra/protobuf extra/python-protobuf'

So may be one of them is required by google-chrome to work properly.

@yochananmarqos This package follows the stable release channel of the Google Debian releases. So as soon as they deem the version stable and put it on the stable channel it will be updated here.

@luzifer: Not sure if you want to update to "Early Stable Updates", but 110.0.5481.77 is now available...early.

EDIT: I'm not sure what the download link is or if it's even publicly available other than server side updates on supported platforms.

@god as the installation script states:

Custom flags should be put directly in: ~/.config/chrome-flags.conf

I cannot start google-chrome

From command line I see the error "dri3 extension not supported"

Browser window flashes up ant then closes.

I have already tried to delete google configuration and start it with the option --disable-gpu.

How about changing the desktop file like below. Without that option, if I enable Wayland (about:flags, Preferred Ozone platform = Auto), I cannot type foreign languages using Fcitx5. If I manually modify the desktop file, when Chrome gets updated, the change gets lost. Are there any downsides of that option? I don't know exactly, but even if that option is specified, if GTK 4 is not available, won't it fall back to GTK 3 anyway?

Exec=/usr/bin/google-chrome-stable --gtk-version=4 %U

@luzifer and BTW, https://bugs.chromium.org/p/chromium/issues/detail?id=409922 is WONTFIX because fontconfig does what it is supposed to do. https://bugs.archlinux.org/task/41795 is TBH, spurious.

@luzifer, you don't need to hard code it. Fontconfig work is, among other things, to do font substitition and Google Chrome works perfectly fine with the ChromeOS fonts (as it has been my experience with my Chromebook).

@toropisco as the Chromium source code (as also reflected in the Chromium package) strongly depends on the liberation font while almost no mentions of the fonts contained in the croscore package are found, liberation will stay a dependency of this package.

Hi, would you mind changing the ttf-liberation dependency in this package and the other beta and dev packages to the ttf-font meta-package or, at the very least, to ttf-croscore? As it is now, the ttf-croscore package (the default fonts in Google's ChromeOS) is in the extra repository while ttf-liberation has been demoted to community (it hasn't been updated in some 10 years now). Ideally, ttf-font is the best for choice reasons, but ttf-croscore is the best for consistency and coherency; it is based on Liberation and has been actively maintained till today.

I'm getting: Failed to generate google-chrome information While trying to update with Manjaro
Never, mind ...
I found the answer below:
For anyone else who is experiencing this issue:

Hi Google-chrome dark-mode:

1. "chrome://flags/"
2. search "Auto Dark Mode for Web Contents"
3. mark field "Enabled" or "chrome://flags/#enable-force-dark" ENTER

For anyone else who is experiencing "Failed to generate google-chrome information" issue: Open Pamac, click three lines at top right, click "preferences", click "third party", then click "clean" at the bottom, this cleans the build directory and fixes the problem, your Chrome will now update with no issues. There's probably a terminal command for this also.

I have installed chrome 106.0.5249.103-1 on manjaro, but dark mode doesn't work in settings (chrome://settings/) (works fine in other sites that support dark mode)?

I have added --force-dark-mode to the arguments.

What should I do to fix this problem?

Hi, I'm getting this chrome_crashpad_handler in google-chrome over and over again in Task Manager Xfce:

/usr/share/skypeforlinux/chrome_crashpad_handler --monitor-self-annotation=ptype=crashpad-handler --no-rate-limit --database=/home/visious/.config/skypeforlinux/Crashpad --url=appcenter://generic?aid=70b7a841-531e-4f9a-9b55-ff40f9d0fb67&iid=1edba44e-484c-407d-c344-86311a28eed0&uid=1edba44e-484c-407d-c344-86311a28eed0<##>aria://?_event=main_crashed&_token=a173030604a34bdcbf21ca59134c7430-2a34e3b5-60e1-4a11-ad6d-2e9eac9ac07c-6614&CrashType=native_crash&DeviceInfo.Id=1edba44e484c07dc34486311a28eed02&DeviceInfo.OsName=Linux&DeviceInfo.OsVersion=5.19.12-arch1-1&Platform_Id=1431&Platform_Uiversion=1431/8.88.0.401/ --annotation=_companyName=Skype --annotation=_productName=skypeforlinux --annotation=_version=8.88.0.401 --annotation=lsb-release=Arch Linux --annotation=plat=Linux --annotation=prod=Electron --annotation=ver=19.0.9 --initial-client-fd=42 --shared-client-connection

$ pacman -Qi google-chrome Name : google-chrome Version : 106.0.5249.61-1 Description : The popular and trusted web browser by Google (Stable Channel) Architecture : x86_64 URL : https://www.google.com/chrome Licenses : custom:chrome Groups : None Provides : None Depends On : alsa-lib gtk3 libcups libxss libxtst nss ttf-liberation xdg-utils Optional Deps : pipewire: WebRTC desktop sharing under Wayland kdialog: for file dialogs in KDE gnome-keyring: for storing passwords in GNOME keyring kwallet: for storing passwords in KWallet Required By : None Optional For : None Conflicts With : None Replaces : None Installed Size : 286.14 MiB Packager : Unknown Packager Build Date : Thu 29 Sep 2022 03:08:51 PM EEST Install Date : Thu 29 Sep 2022 03:09:22 PM EEST Install Reason : Explicitly installed Install Script : Yes Validated By : None

PS: skypeforlinux is working well, google-chrome crashes.

Hi.

Somehow, upgrading this from 104.0.5112.79-1 to 105.0.5195.102-1 breaks the ability to write special characters (ñ, ç, á, à...) in textboxes when using Ozone/Wayland.

This has been reported at https://bugs.chromium.org/p/chromium/issues/detail?id=1360070, I'm just posting this so anyone who comes here with the same problem knows this is the cause.

What does the make google chrome the default browser checkbox do when you first start this program?

@PC2022 I don't know if it is related but I have --password-store=basic in my ~/.config/chrome-flags.conf wo any problems in xfce + xfwm4 4.16. Passwords stored in plain text(basic mode) are not encrypted! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md

Ever since I started using arch (and google-chrome-stable), I find that Chrome quickly forgets cookies and login sessions, so I have to re-login to many sites several times a day.

It is unrelated to upgrading Chrome, or even rebooting.

Unfortunately it's very unpredictable, sometimes it seems to lose cookies after an hour or two, and other times after a day or two. It is not due to the site setting a short cookie expiry, since it affects github, Amazon etc

A week or two ago I added --password-store=gnome to ~/.config/chrome-flags.conf, as I saw someone suggest it as a solution, but it hasn't made a difference.

Any tips on how I can fix or at least troubleshoot this? Im using awesomewm as my WM, with xfce desktop, and a few basic gnome services running.

@esiqveland, I know it's been a few months now, but I had the exact issues you've described on a fresh Chrome execution where there was nothing in ~/.config.

I have composition completely disabled in /etc/X11/xorg.conf due to some issues I was having in a few games. The "fix" was to remove the line from xorg.conf, reboot, run Chrome and disable hardware acceleration, then I was able to add the line back, reboot and use Chrome as required.

If you have composition disabled in xorg.conf like I do and you have no idea why, you'd probably be best to remove the line and leave it. I only have it there for specific reasons.

Replace ability to disable Side Panel Button. Its not used.

103.0.5060.53-1 Playing netflix DRM content，sometimes has problems

Anybody else's extension popup's very narrow to the extent they're unusable, with no way to make them wider?

Hi, I'm on 102.0.5005.115-1 and I have a problem saving files with "Save As", when the dialog opens and I try to change the name of the file to save, the focus shifts to the search in the same window, and then I have to click back in the name field. I type one letter and it immediately goes back to search. I have to click back to the name field for each letter I want to type for the file name. Anyone else?

P.S. typing the name in the search field, cutting and pasting in the name field works, but it's certainly not the expected behaviour. Also worth mentioning that the Save As dialog pops up unfocused

Downgrading to 101.0.4951.64 (which is the latest 101 stable release) fixes the tab dragging issue.

@rcqwerty I'm also having the tab-dragging/reordering issue, again. Looks like a bug regression in 102...

Having the same problem in 102.0.5005.61-1 as we had in version 97.0.4692.71 -- as soon as I drag a tab 1 pixel it pops out into a new window, and cannot re-attach the tab.

@JP-Ellis works fine for me using makechrootpkg as well as building in a clean docker container (my default way to build the package).

It appears that the PKGBUILD does not include $pkgname.install in the list of sources despite requiring it. As a result, this package does not correctly build in a chroot environment as $pkgname.install is copied into the chroot environment.

To check the error, try building the package through makechrootpkg instead of makepkg.

EDIT: I actually believe this might be an error with makechrootpkg as the PKGBUILD man page does say that .install files should automatically be added to the source files. I will report this upstream.

To enable chrome://flags/#enable-reader-mode First activate this flag chrome://flags/#temporary-unexpire-flags-m100

I am running production version:

Google Chrome 101.0.4951.54 (Official Build) (64-bit) Revision 67da1aeb32cedd27634ca6634fb79cbd85d3f0ab-refs/branch-heads/4951@{#1126}

It seems that chrome://flags/#enable-reader-mode is nowhere to be found.

Please advise and thank you for all that you do!! Cheers. DTS

What is the purpose of the "StartupWMClass" fix, and is it possible to drop it? The chromium.desktop in the official chromium package does not seem to have this line.