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.

Since around June 12th, I have been experiencing regular crashes using this google-chrome package, where chrome just randomly disappears with no warning, and then emits a core dump.

Checking my update log, this corrresponds to when I updated to 137.0.7151.103-1 on 11th June

Im using Arch and KDE Plasma 6.4.0. Curious to see if anyone else is seeing this same issue

$ ls -ltr /var/lib/systemd/coredump/ | grep chrome
-rw-r-----+ 1 root root 45237278 Jun 12 20:56 core.chrome.1000.a4295aaf020140e1afb4c0b7b432b6b3.398315.1749758183000000.zst
-rw-r-----+ 1 root root 44027259 Jun 17 09:35 core.chrome.1000.1aa6b95cac0c4c089ea6efbb7f2fd497.840098.1750149334000000.zst
-rw-r-----+ 1 root root 46209507 Jun 17 11:10 core.chrome.1000.1aa6b95cac0c4c089ea6efbb7f2fd497.864129.1750155015000000.zst
-rw-r-----+ 1 root root 48201588 Jun 19 00:12 core.chrome.1000.1d9d9c654ced40d79f420af4744f16a5.484985.1750288338000000.zst
-rw-r-----+ 1 root root 46506255 Jun 23 02:07 core.chrome.1000.da00d926e4e5429699e14291e0d23615.491304.1750640825000000.zst
-rw-r-----+ 1 root root 23700372 Jun 23 03:06 core.chrome.1000.da00d926e4e5429699e14291e0d23615.567255.1750644397000000.zst
-rw-r-----+ 1 root root 51935727 Jun 27 03:05 core.chrome.1000.92adc1ce994347c19b808282803c680c.856576.1750989929000000.zst

$ cat /var/log/pacman.log | grep chrome | grep 'upgraded' | tail -n3
[2025-06-03T18:08:59+0100] [ALPM] upgraded google-chrome (137.0.7151.55-1 -> 137.0.7151.68-1)
[2025-06-11T18:17:34+0100] [ALPM] upgraded google-chrome (137.0.7151.68-1 -> 137.0.7151.103-1)
[2025-06-21T20:34:43+0100] [ALPM] upgraded google-chrome (137.0.7151.103-1 -> 137.0.7151.119-1)

$ cat /var/log/pacman.log | grep 'plasma-desktop' | tail -n6
[2025-06-03T12:42:36+0100] [ALPM] upgraded plasma-desktop (6.3.4-1 -> 6.3.5-1)
[2025-06-21T20:32:49+0100] [ALPM] upgraded plasma-desktop (6.3.5-1 -> 6.4.0-1)

I havent seen any chrome bug reports so wonder if its somehow package related?

Hello,

I would like to report an issue with how the current launcher script for google-chrome-stable handles the ~/.config/chrome-flags.conf configuration file.

At present, the script does not read the file line by line, but instead merges all flags into a single line. This causes problems when using flags that contain spaces. For example, if I add the following line to ~/.config/chrome-flags.conf:

--user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

Upon launching Chrome, each word after the first space is interpreted as a separate argument, resulting in multiple unwanted tabs opening (such as "(Windows", "NT", "10.0;", etc.).

It would be much appreciated if the script could be updated to read and pass each line from chrome-flags.conf as a separate argument, similar to how the Arch Chromium package handles its flag files. This would allow flags with spaces—like user-agent strings or proxy settings—to be properly parsed and used.

Thank you very much for your work in maintaining this package and for considering this suggestion.

I've the same problem of @ms178. After the latest arch updates, Chromium -based browsers are slow to open up

It seems that the problem is kwallet, if you use the flag --password-store=basic the browser opens immediately

• https://bugs.kde.org/show_bug.cgi?id=504014

• https://bbs.archlinux.org/viewtopic.php?id=305540

@admalledd Thanks, I've re-installed my system and got it to work until the KDE package upgrades from today broke Google Chrome and all related browsers again. They now take a very long time to start up:

[173978:173978:0511/192046.768251:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [173978:173978:0511/192046.768311:ERROR:components/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled) [173978:173978:0511/192046.768701:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable [173978:173978:0511/192046.768721:ERROR:components/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6

@ms178 I was experiencing the same issue, but seems to have been solved by uninstalling then reinstalling this AUR package.

Small update to my post from 2025-04-01, every released version past 134.0.6998.165 from this repo does still crash on startup on my system. However, I don't see any crashes with a Chromium build from RobRich999 (AVX2) 137.0.7129.0 from his Github repo.

@cbrnr

I cannot enter special characters (e.g., backticks) in the current version. Does anyone else have this problem?

Yes. I think this is reported here: https://issues.chromium.org/issues/407944200

Edit: Issue has been fixed since 135.0.7049.79. However, at least on Gnome Wayland, it is still necessary to use --enable-features=WaylandTextInputV3.

Edit2: Since 135.0.7049.95, --enable-features=WaylandTextInputV3 is no longer needed.

On 135.0.7049.52-1 after restarting the browser, you need to authenticate with your Google account every time.

Same. It resets all cookies, and doesn't sync passwords. Do not update. In my case downgrading to the previous version from the yay cache helped (but need to log in everywhere again).

I cannot enter special characters (e.g., backticks) in the current version. Does anyone else have this problem?

On 135.0.7049.52-1 after restarting the browser, you need to authenticate with your Google account every time.