Package Details: google-chrome 131.0.6778.85-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2247
Popularity: 9.36
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-19 19:19 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)

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.

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 157 Next › Last »

mattj commented on 2022-02-05 22:08 (UTC)

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?

BachoSeven commented on 2022-02-05 12:58 (UTC)

Thanks for finding that out, @koshikas!

koshikas commented on 2022-02-03 06:45 (UTC) (edited on 2022-02-03 07:15 (UTC) by 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

babam commented on 2022-01-30 17:40 (UTC)

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

ryuukk commented on 2022-01-30 02:16 (UTC)

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

luzifer commented on 2022-01-29 15:09 (UTC)

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

H0301ein commented on 2022-01-28 19:04 (UTC)

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

alexey2baranov commented on 2022-01-26 08:29 (UTC) (edited on 2022-01-26 08:29 (UTC) by alexey2baranov)

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

alexey2baranov commented on 2022-01-26 08:26 (UTC)

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 :(

bobarch64 commented on 2022-01-20 06:00 (UTC)

@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

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 157 Next › Last »