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.

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.

135.0.7049.52 crashes for me at startup on CachyOS with: %U --use-gl=angle --use-angle=vulkan --enable-features=Vulkan,DefaultANGLEVulkan,VulkanFromANGLE,VaapiVideoDecodeLinuxGL,VaapiIgnoreDriverChecks,VaapiVideoEncoder --enable-accelerated-mjpeg-decode --enable-global-vaapi-lock --use-gpu-scheduler-dfs --cast-streaming-hardware-h264 --enable-zero-copy

Reverting back to 134.0.6998.165-1 solves the issue for me.

                                            Stack trace of thread 13433:
                                            #0  0x000057198b41add9 mi_free (libmimalloc.so.2 + 0x21add9)
                                            #1  0x000057196eb18798 n/a (libQt6Core.so.6 + 0x318798)
                                            #2  0x000057196eb1c4c0 _ZNK13QSystemLocale5queryENS_9QueryTypeEO8QVariant (libQt6Core.so.6 + 0x31c4c0)
                                            #3  0x000057196ea1d74c n/a (libQt6Core.so.6 + 0x21d74c)
                                            #4  0x000057196ea1def5 _ZN7QLocaleC2Ev (libQt6Core.so.6 + 0x21def5)
                                            #5  0x000057196e93986d _ZN9QResourceC1ERK7QStringRK7QLocale (libQt6Core.so.6 + 0x13986d)
                                            #6  0x000057196e8e9d43 n/a (libQt6Core.so.6 + 0xe9d43)
                                            #7  0x000057196e8ea07a n/a (libQt6Core.so.6 + 0xea07a)
                                            #8  0x000057196e8eaf0a _ZN19QLibraryInfoPrivate5pathsEN12QLibraryInfo11LibraryPathENS_9UsageModeE (libQt6Core.so.6 + 0xeaf0a)
                                            #9  0x000057196e8ebc37 _ZN19QLibraryInfoPrivate4pathEN12QLibraryInfo11LibraryPathENS_9UsageModeE (libQt6Core.so.6 + 0xebc37)
                                            #10 0x000057196ec3366a n/a (libQt6Core.so.6 + 0x43366a)
                                            #11 0x000057196e92e015 _ZN16QLoggingCategoryC1EPKc9QtMsgType (libQt6Core.so.6 + 0x12e015)
                                            #12 0x000057196f1a6215 n/a (libQt6Gui.so.6 + 0x1a6215)
                                            #13 0x000057196f1a93c5 _ZN15QHighDpiScaling18initHighDpiScalingEv (libQt6Gui.so.6 + 0x1a93c5)
                                            #14 0x000057196f194dcd _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x194dcd)
                                            #15 0x000057196f1970b8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1970b8)
                                            #16 0x000057196e962a05 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x162a05)
                                            #17 0x000057196f19715f _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x19715f)
                                            #18 0x000057196faf9b2e _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0xf9b2e)
                                            #19 0x000057198fe5c0c7 n/a (libqt6_shim.so + 0x40c7)
                                            #20 0x000057198fe5dbe2 CreateQtInterface (libqt6_shim.so + 0x5be2)
                                            #21 0x00005719a0f237d3 n/a (/opt/google/chrome/chrome + 0xc9757d3)
                                            #22 0x00005719a0f13ab5 n/a (/opt/google/chrome/chrome + 0xc965ab5)
                                            #23 0x000057199a93eeaf n/a (/opt/google/chrome/chrome + 0x6390eaf)
                                            #24 0x000057199a93f767 n/a (/opt/google/chrome/chrome + 0x6391767)
                                            #25 0x0000571999f26f0a n/a (/opt/google/chrome/chrome + 0x5978f0a)
                                            #26 0x000057199ae2d241 n/a (/opt/google/chrome/chrome + 0x687f241)
                                            #27 0x000057199ae2dd6f n/a (/opt/google/chrome/chrome + 0x687fd6f)
                                            #28 0x0000571997fa6010 n/a (/opt/google/chrome/chrome + 0x39f8010)
                                            #29 0x00005719995d6b7c n/a (/opt/google/chrome/chrome + 0x5028b7c)
                                            #30 0x00005719991ac9f7 n/a (/opt/google/chrome/chrome + 0x4bfe9f7)
                                            #31 0x00005719991ad327 ChromeMain (/opt/google/chrome/chrome + 0x4bff327)
                                            #32 0x000057198ba26f87 n/a (libc.so.6 + 0x26f87)
                                            #33 0x000057198ba27037 __libc_start_main (libc.so.6 + 0x27037)
                                            #34 0x000057199b49c68a _start (/opt/google/chrome/chrome + 0x6eee68a)

I've been experiencing Google Chrome continuously crashing (after a few minutes, but sometimes after a few seconds) in KDE Plasma (I'm pretty sure it works in Gnome), both in Wayland and in X11. This is what is shown running Chrome from the command line when it crashes:

[0313/150631.952661:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0313/150631.959022:ERROR:process_memory_range.cc(75)] read out of range
[1]    6358 trace trap (core dumped)  google-chrome-stable

@kosa You might have the same problem as me. After downgrading Mesa to version 24.2.7, I have no more system freezes when I use google chrome.

[stone@archlinux ~]$ google-chrome-stable 
Created TensorFlow Lite XNNPACK delegate for CPU.
[9063:9091:1212/213433.391647:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
[9122:9139:1212/213442.959414:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -100
[9122:9139:1212/213453.513320:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -100
[9063:9091:1212/213453.513611:ERROR:connection_factory_impl.cc(434)] Failed to connect to MCS endpoint with error -100
[9148:1:1212/213458.654662:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[9063:9063:1212/213458.656013:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=512
[9063:9091:1212/213503.163176:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
[9063:9063:1212/213528.819761:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=512
[9063:9091:1212/213545.730790:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
[9063:9063:1212/213558.981308:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=512
[9154:7:1212/213559.101369:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[9148:7:1212/213559.101691:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[9063:9091:1212/213619.531026:ERROR:connection_factory_impl.cc(483)] ConnectionHandler failed with net error: -2
Warning: /usr/lib32/libvulkan_intel_hasvk.so: 错误的 ELF 类：ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib32/libvulkan_intel_hasvk.so. Ignoring this JSON
Warning: /usr/lib32/libvulkan_intel.so: 错误的 ELF 类：ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib32/libvulkan_intel.so. Ignoring this JSON
Warning: /usr/lib32/libvulkan_intel_hasvk.so: 错误的 ELF 类：ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib32/libvulkan_intel_hasvk.so. Ignoring this JSON
Warning: /usr/lib32/libvulkan_intel.so: 错误的 ELF 类：ELFCLASS32
Warning: loader_icd_scan: Failed loading library associated with ICD JSON /usr/lib32/libvulkan_intel.so. Ignoring this JSON
Warning: Old MapAsync APIs are deprecated. If using C please pass a CallbackInfo struct that has two userdatas. Otherwise, if using C++, please use templated helpers.
[9122:9139:1212/213631.782070:ERROR:ssl_client_socket_impl.cc(878)] handshake failed; returned -1, SSL error code 1, net_error -100
[9063:9063:1212/213636.351154:ERROR:wayland_event_watcher.cc(47)] libwayland: warning: queue 0x2c140221c800 destroyed while proxies still attached:

[9063:9063:1212/213636.351221:ERROR:wayland_event_watcher.cc(47)] libwayland:   wl_shm_pool#46 still attached

It takes a long time to open Chrome. Even if it is opened, it is too laggy

Also getting some hard crashes recently (all gnome freezes, then crashes), using wayland with the following flags:

$ cat ~/.config/chrome-flags.conf --disable-features=HardwareMediaKeyHandling --enable-features=UseOzonePlatform --ozone-platform=wayland

I also noticed green bugs/flickering on pictures or videos (in google meet), notably when browsing this website: https://arc.net (sorry if it crashes your computer !)

My platform is Intel i7-6700 and nvidia GeForce GTX 1060 with proprietary driver 565.57.01-6

Hi all. I'm running google-chrome 131.0.6778.69-1 after updating recently. Something must have happened with this package in the past month.

The GDK_DPI_SCALE setting has no effect, and my icons and fonts are too small. I've tried much bigger values of GDK_DPI_SCALE and it has no effect anymore.

I set --ozone-platform=wayland in the Chrome flags again (which was reset to X11) and restarted, and also tried passing that switch manually along with the GDK_DPI_SCALE.

In the past, I've set this GDK_DPI_SCALE with env GDK_DPI_SCALE=1.75 google-chrome-stable in the Exec lines in its /usr/local/applications/google-chrome.desktop file (or more specifically the one in ~/.local/share/applications). But just to make sure, I also set a system-wide setting for this in .bashrc and .zshenv, logged out and logged back in, and made sure it was indeed set. This still has no effect (and is undesirable, because many other applications have their scale wrong, as a result).

• google-chrome 131.0.6778.69-1
• wayland 1.23-1-1
• gtk3 1:3.24.43-4
• sway 1:1.10-1

After upgrading chrome to version 130.0.6723.91-1 and restarting my system, I tried to start chrome again, and my system froze. The only option was to hard reset my computer.

After restarting, I started chrome again, and all of my previous browsing session was erased. I could not bring it back with Ctrl+Shift+T as usual. Soon it froze and I had to hard reset again.

I have two separate Chrome profiles. I started the second one, and my last session for that was there. The system froze about a minute after I had launched chrome, and I had to hard reset a third time.

The fourth time that I launched chrome (profile #2) my previous browsing session was gone also, and after it froze again, and I hard reset my system, I restarted my computer for the fifth time.

I haven't started chrome yet, and it's been close to an hour now. My system runs perfectly fine. What can I try?

Get this when running google-chrome-stable --ozone-platform=wayland on KDE Plasma v6.2.1 (Wayland). Eventually chrome loads after 20-30 seconds:

[8367:8367:1018/141454.839532:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.839616:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.839706:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.839790:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.839881:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.839966:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.840050:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.840136:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.840220:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)
[8367:8367:1018/141454.840304:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: No such file or directory (2)

Does 129.0.6668.70-1 lag for everyone or just me? For example, Reddit scrolling is noticeably not smooth, and Claude workbench lags as hell on typing on a quite powerful PC (i9-14900K, 128 gigs of RAM, fast nvme ssd and rtx 4070s). The previous version was working fine. UPD: HW acceleration stopped working for some reason.

@mike cloaked, no this message is generally observerd all over arch packaging.

When building chrome from current version I see:

==> Tidying install...
  -> Removing empty directories...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
libfakeroot internal error: payload not recognized!

The package does still build and chrome runs fine - but I wonder if the libfakeroot command line error message can be fixed by any change in the PKGBUILD? I have seen similar error reports concerning libvirt (eg https://bbs.archlinux.org/viewtopic.php?id=298643).

The new Google Chrome version is freezing for me.

--gtk-version=4 does not work with fcitx5, use --gtk-version=3 to fix this,my flags: google-chrome-stable --ozone-platform=wayland --enable-features=ozone --enable-wayland-ime --disable-features=WaylandFractionalScaleV1 --gtk-version=3

@Comodin, please supply the actual full error message and surrounding logs. Like this we will not be able to help you! Also please familiarize yourself with the process of installing packages without and AUR helper and see if the problem pops up with the methods described there aswell: https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages

error to install: [/home/comodin/.cache/yay/google-chrome/google-chrome-124.0.6367.155-1-x86_64.pkg.tar.zst] - exit status 1

Currently, --gtk-version=4 won't work (Chrome loads GTK3). This makes IME unusable under Wayland.

Apparently, if you modify the wrapper script at /opt/google/chrome/google-chrome to either comment out export LD_LIBRARY_PATH or prepend /usr/lib to it, this CLI flag starts working and it starts loading GTK4.

Am I the only one with broken emojis on certain sites - like this one: https://emojipedia.org/money-with-wings ? It is broken just on the title

Adding these lines to ~/.config/chrome-flags.conf resolved the issue for me:

--enable-features=UseOzonePlatform
--ozone-platform=wayland

@integer_32 - not for me, no

Is that wayland issue resolved in 124.0.6367.91-1?

Have the same issue

sway 1:1.9-3 google-chrome 124.0.6367.78-1 linux-zen 6.8.7.zen1-1 xf86-video-amdgpu 23.0.0-2

@bassadin - huge thanks for the workaround with about://restart, you saved my mood!

But seems like should be fixed with next upgrade 🤞

@gromit yep, Plasma 6.0.4 with Wayland :)

@bassadin are you on Wayland?

Since a few updates, my Chrome windows are invisible at launch until I blindly type "about://restart" into a new tab. Is this the same issue with the ozone platform that you are talking about?

Would you please consider putting up a google-chrome-debug PKGBUILD? Debug symbol files for Chrome are public and can be downloaded, see: https://issues.chromium.org/issues/41141025#comment44.

For me google-chrome-beta (125.0.6422.4) shows up normally and as wayland surface (without any switch/config needed), maybe next release will fix this white screen issue ...

facing the ozone platform = wayland issue. the browser windows do not show.

@ciupenhauer, honestly I think that updating + adding the --ozone-platform=wayland option to the launch options is the best option.

@Edu4rdSHL thanks for all the links. Doesn't look like this will get solved anytime soon, it's been reported since march. Downgrading seems the best option

need to add CHROME_WRAPPER environment variable so that the PWA application startup icon gets the correct exec path.

export CHROME_WRAPPER="`readlink -f "$0"`"

Avoid updating to version 124 if you use Wayland. It doesn't work there since the beta. https://aur.archlinux.org/packages/google-chrome-beta#comment-963012

Edit: here's the upstream report: https://issues.chromium.org/issues/329678163

It only seems to affect if you have set the option from chrome://flags/, if you manually run google-chrome-stable --ozone-platform=wayland from the command line, it works.

If you only build for yourself, look here: https://bbs.archlinux.org/viewtopic.php?pid=1000549#p1000549

Like others I had noticed the very long time on the final compression in recent months that was taking a minute or so. I looked at the thread at https://www.reddit.com/r/archlinux/comments/1bwyv1q/how_do_you_fix_zstds_slowness/ and decided to change the COMPRESSZST in .config/pacman/makepkg.conf to COMPRESSZST=(zstd -c -T4 -8 -) and now when I run the chrome browser build it takes a second or so to do the compression. The final .zst file is now 130M instead of the 112M when using the standard ultra compression, but for me the file size is less important than the very long compression time. I thought I would pass this on in case others might wish to do something similar.

ibus not works in wayland mode, even set "--gtk-version=4" option.. "--gtk-version=4" option works well in previous version.

In Chrome Stable version 123, the RawDraw option will result in blank screen. This problem has reproduced in my GNOME 45/46 environment with Mutter 45/46, my machine spec is Intel UHD 620 with Mesa 24. Just for a reference.

Has anyone experienced save/open file picker dialogs not opening after updating to 123.0.6312? Same problem on Chrome and Chromium. I have xdg-desktop-portal installed. It's possible I caused this by messing around with something else and not the update. The debug log says:

[145164:145196:0326/161840.429311:VERBOSE1:bus.cc(916)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s

string "org.freedesktop.portal.Desktop"

[145164:145196:0326/161840.522535:VERBOSE1:object_proxy.cc(513)] Signal received: message_type: MESSAGE_SIGNAL
destination: :1.8953
path: /org/freedesktop/portal/desktop/request/1_8953/handle_2
interface: org.freedesktop.portal.Request
member: Response
sender: :1.12
signature: ua{sv}
serial: 220

uint32_t 2
array [
  dict entry {
    string "uris"
    variant       array [
      ]
  }
]

@nfs did you install the base-devel package? It's a requirement for building AUR packages.

When I try to build this, I get:

==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.