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 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.