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 had the same issue with v100.0.4896.75 and v100.0.4896.60.

With v100.0.4896.88 everything should be fine.

No problem for me, everything working

>>esiqveland commented on 2022-04-10 15:12 (EEST)

>>I have had major issues with crashes and severe graphical glitches since about Chrome #>>97.x, but the latest 100.x does not even start anymore. Anyone else having issues?

I have had major issues with crashes and severe graphical glitches since about Chrome 97.x, but the latest 100.x does not even start anymore. Anyone else having issues?

The latest version 100.0.4896.60-1 crashes on startup. Also as per @openmindead below, cannot restore saved tabs on start and fails to restart if clicked on restore button. Don't upgrade.

google-chrome-stable 
[2483:2483:0402/153500.884489:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[0402/153505.840407:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0402/153505.841439:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Trace/breakpoint trap (core dumped

Had to downgrade to version 99.0.4844.74, the latest version kept my CPU at 100% usage, with only 1 tab open, as well as not closing even with "Allow running in background" disabled, I had to manually kill it every time, using killall, already submitted a bug report to Google.

Getting rendering issues as of version 100.0.4896.60-1. Turning of hardware acceleration fixed it if anyone else is seeing the same issues.

The latest version 100.0.4896.60-1 cannot restore saved tabs on start and fails to restart if clicked on restore button. Be careful folks. The issue is pertinent to deb package itself (same issue in Ubuntu).

There are 2 ways to deal with it: wipe ~/.config/google-chrome and start from scratch, or just downgrade.

@yochananmarqos: The package was automatically downgraded after Google pulled 99.0.4844.51 from the stable channel of their repository… As we're just re-packaging the Debian version this package follows the most recent version available in the official repo… That one downgraded between Mar 2, 2022 1:43 PM and 2:10 PM UTC…

Current state as of 4:10 PM UTC is still v98:

Package: google-chrome-stable
Version: 98.0.4758.102-1

(Still it's indeed an interesting question why v99 was pulled from the stable channel…)

@luzifer: Why did you revert back to 98?

WebGL is no longer working with the latest updates:

pacman -Qi google-chrom

Name : google-chrome Version : 98.0.4758.102-1

core-dump: process 12440 (chrome) of user 1026 dumped core.
Module linux-vdso.so.1 with build-id 2ad6b24b487ac2a9c2901c8ddf457eeb465c1d5a

Module libicudata.so.70 with build-id e1dcc2a88cfaafed882d09c90c668af0eed4efed

Module libicuuc.so.70 with build-id 2e245c2bf12f95fd8ab79b3a4be99524677cbd70

Module libxml2.so.2 with build-id b710b880b0d4e9c93554fa632129db44c20632cd

Module libncursesw.so.6 with build-id 1f873ddb2c32ab39d0b7d8646d03680ffe99de7c

Module libedit.so.0 with build-id 4b0babfcad161c2ad0af6e59e2493258db23a331

Module libxcb-dri2.so.0 with build-id 2dd6e65129a809dab828a1d26215a3f7a363fcc8

Module libdrm_nouveau.so.2 with build-id af8afb2331ac08c52132102ecbdc6076a8eb4c6f

Module libdrm_amdgpu.so.1 with build-id 8eb3977b830f3012d9ead7b4def5f4d2f38ec688

full dump can be sent

Is anyone experiencing the issue where on anything after Version 94.0.4606.71 in XFCE you lose the ability to adjust the window size on the sides of the window and you can only do so from the corners?

With chrome 98.0.4758.80-1, Wayland, and the flags --enable-features=UseOzonePlatform --ozone-platform=wayland --ignore-gpu-blocklist --enable-zero-copy --enable-gpu-rasterization --enable-accelerated-video-decode --enable-features=VaapiVideoDecoder --password-store=kwallet5 the window zooms in about 4x on start after being interacted with. Anybody else getting this?

Thanks for finding that out, @koshikas!

anyone else experiencing video-acceleration disabled since new chrome-98

Contents of chrome://gpu: Video Decode: Hardware accelerated

Video Acceleration Information Decoding (Legacy VideoDecodeAccelerator)
Decode h264 baseline 16x16 to 4096x4096 pixels Decode h264 main 16x16 to 4096x4096 pixels Decode h264 high 16x16 to 4096x4096 pixels

but under developer tools and intel_gpu_top no hardware acceleration is utilized.

EDIT; adding --disable-features=UseChromeOSDirectVideoDecoder got the hardware acceleration working again. now the Video Acceleration Information reads as;

Video Acceleration Information Decoding (VideoDecoder) Decode h264 baseline 16x16 to 4096x4096 pixels Decode h264 main 16x16 to 4096x4096 pixels Decode h264 high 16x16 to 4096x4096 pixels Decoding (Legacy VideoDecodeAccelerator)
Decode h264 baseline 16x16 to 4096x4096 pixels Decode h264 main 16x16 to 4096x4096 pixels Decode h264 high 16x16 to 4096x4096 pixels Encoding

@ryuukk Chrome on Linux can only use HW acceleration if using an extension like NotYetAV1 or enhanced-h264ify.

Please update it so the process starts with:

google-chrome-stable --use-gl=desktop --enable-features=VaapiVideoDecoder

by default, so we get video decode HW accelerated by default, that should be the default that everyone should expect

otherwise people think linux is trash because no HW accell for videos, it feels bad

@H0301ein hmm looks like the flag might does no harm (cannot test it myself) but that would be the first flag the package itself overrides from the default distribution… At moment the browser is delivered as Google packages it (with minor patches to the desktop file which I'm also hesitant to implement) while it allows users to override flags themselves using a simple config file. Looking at the chromium package the flag is set to its default value too. Therefore following this chain of arguments I'd not override that flag in the package itself. Every user can set the flag easily in their ~/.config/chrome-flags.conf and we're not sticking to an old patch when upstream changes the default value of that flag…

@luzifer i think it's good if add flag --ozone-platform-hint=auto to /bin/google-chrome-stable for run in both X11/wayland

hm. but after remove and install it becomes v97:)

As I read at https://chromereleases.googleblog.com/search/label/Stable%20updates January 19, 2022 The Stable channel has been updated to 97.0.4692.99 for Windows, Mac and Linux

Today in this repo I see v90.0.4430 :(

@babam, maybe this is not the best place to find info on hardware acc. But better look here: https://bbs.archlinux.org/viewtopic.php?id=244031&p=25

Is Chrome+Youtube able to use hardware acceleration (X11)?

In my case Chrome+Youtube can only use the hardware acceleration if I install the NotYetAv1 extension.

FFmpeg+MPV uses hardware acceleration when playing AV1 videos.

Thanks.

My youtube ad block addon is also not working properly after the update (of course and the tab drag and drop function), is it just me?

For any other Arch newbies who installed with yay and are struggling to figure out how to apply the instructions in the Wiki, perhaps I can save you a bit of time.

Assuming you've installed a prior version of chrome with yay, and haven't disabled the yay cache, yay should have cached it in ~/.cache/yay. If you do have a previously cached version, you can use the pacman command from the wiki to roll back using that path instead:

# pacman -U .cache/yay/google-chrome/google-chrome-96.0.4664.110-1-x86_64.pkg.tar.zst

google-chrome-dev 99.0.4818.0-1 still has the bookmark/tab bug google-chrome 96.0.4664.110-1 works fine

I just downgraded to 96 to fix bookmarks issue. and let's wait for 99 release.

All drag and drop issues fixed in version 99, currently google-chrome-dev AUR package.

Never in my life have I thought that I would need to run development version of a program to have working drag and drop. For a moment, I considered moving to Gecko or even using Windows for internet activity...

Either pull version 99, or say on version 94 as long as possible.

Drag and drop on bookmark bar is not working. Some fix?

It looks like the mouse cursor is not hiding on fullscreen video playback for 97. 96 works fine.

FYI, while we wait for the moving tabs w/ mouse bug to be fixed, you can use keyboard shortcuts to work around the issue.

CTRL + SHIFT + PAGE UP/DOWN

@yochananmarqos

This method I shared solved my problem. Using this package didn't enable me, for example, to use Whatsapp in a different window like a different app. I'm on KDE Plasma X11.

https://ibb.co/SfgD65B

Why it solved or the logic behind that didn't really bother me lol

Just sharing in case anyone stumbles on the same problem.

@metabee: This package uses the official DEB package, using debtap makes no sense.

There are no AUR helpers including pacaur in the Arch repos, they can't be installed with pacman. Installing one AUR helper to install another AUR helper doesn't make any sense.

This package doesn't allow to use chrome apps as separate apps. I instead built the .deb chrome install from the chrome official webpage using pacaur to install yay, yay to install debtap and debtap to install chrome.

sudo pacman -S pacaur

pacaur -S yay

yay -S debtap

debtap -u

cd <<<<<<<FILE WHERE THE CHROME INSTALL WAS DOWNLOADED>>>>>>

debtap <<<<<<<NAME OF THE CHROME FILE.DEB>>>>>>>

sudo pacman -U <<<<<NAME OF THE FILE BUILT BY DEBPTAP>>>>>>>

now I can use chrome desktop apps

Cant move tabs around and cant move around bookmarks after the last update

I experienced the same problem, not being able to drag around tabs anymore with 97.0.4692.71. Rolling back to chromium-96.0.4664.93 fixed to for me, too.

The issue related to dragging things has been fixed in canary, it is tracked in https://bugs.chromium.org/p/chromium/issues/detail?id=1279532.

Having tab bug w/ Chrome 97 too as well as mouse cursor no longer hiding in fullscreen video mode.

@leddy231 I am having the same problem with version 97.0.4692.71 - as soon as I drag a tab 1 pixel it pops out into a new window.

@leddy231 I have the same problem with moving tabs around I cant rearrange tabs or merge them, downgrading from v97.0.4692.71 to v96.0.4664.110 fixed the problem.

@leddy231 currently experiencing the same tab bug on 97. Running EndeavourOS

Something broke on chrome 97 on a fresh install of Manjaro KDE, it was working fine and then the update some hour ago broke the tabs. I can no longer move tabs around, instead it pops them into a new window, and cant be merged back. Broken on google-chrome 97 and google-chrome-dev 98. Working fine on chromium 96 and google-chrome 96 (previous commit) Gonna see if I can figure out what it is and make a bug report to chromium, but just a heads up if more users report it

@Thundas, it must have broken in a later release, it was occurring on 96.0.4664.110 and 96.0.4664.93, but removing and installing .45 manually fixed it. Thank you for the help.

I'm wondering if this is affecting anyone else. Recently I have been unable to drag Chrome windows to resize them by using the left, right, or bottom edge of the window. The top-left, top-right, and top all work. I should note this is in XFCE.

@yochananmarqos thanks, i switched to yours and its working great, its sad that the update broke angle's hardware decoding.