Package Details: google-chrome 144.0.7559.96-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: 2321
Popularity: 11.82
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2026-01-21 12:39 (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

1 2 3 4 5 6 .. 164 Next › Last »

amstan commented on 2025-12-10 19:22 (UTC)

Can confirm, 143.0.7499.109 fixes the scrolling problem (https://issues.chromium.org/issues/457478032) that got introduced in 143.0.7499.40.

leatherpants commented on 2025-12-10 03:51 (UTC) (edited on 2025-12-10 03:53 (UTC) by leatherpants)

Interestingly, I'd experienced scroll speed problem on Windows 11 on Surface Pro 8 too several days ago. So I think it's a Google's problem. It seems to have been fixed on Windows now, but sadly I didn't realise when and how it got fixed.

marcosfrm commented on 2025-12-07 12:21 (UTC)

The missing minimize, maximize, and close icons are due to a GTK 4.20 compatibility issue, which https://chromium.googlesource.com/chromium/src.git/+/cdc2a57272589f9522689500838e889b88b3f9d4 has patched. This fix is expected to land in the 143 series soon.

84634E1A607A commented on 2025-12-04 04:56 (UTC)

I'm with KDE and I'm experiencing the same issue.

https://issues.chromium.org/issues/457478032

https://chromium-review.googlesource.com/c/chromium/src/+/7171891

Revert "Fix touchpad scroll sensitivity on Wayland."

This reverts commit ded09f2a729ad7d92f404bd9f86fac819f178f8b.

Reason for revert: Users found the slower scroll speed relative to other Wayland applications to be disruptive.

rootAbra commented on 2025-12-03 21:59 (UTC)

I’m experiencing the same issue that @madscience mentioned — two-finger scrolling on my touchpad in Hyprland (Wayland) works fine everywhere except Google Chrome, where it’s extremely slow in the latest version. I’ve also tried toggling smooth scroll on or off, and it doesn’t help.

madscience commented on 2025-12-03 01:51 (UTC)

Is there an issue with scroll speed on the latest version for anyone else? I'm using two-finger scroll on a touchpad in Hyprland (wayland) and the scroll speed is super slow. I've tried w/ smooth scroll off/on? I realize this isn't a packaging issue.

mrjxtr commented on 2025-11-20 00:54 (UTC)

Why is it that every time I launch google chrome, it always tries to open http://google-chrome/ which does not exist btw.

leodip commented on 2025-11-19 08:24 (UTC)

How to fix the lack of icons on the top right corner of the window (minimize, maximize, close):

Chrome Settings -> Appearance -> Change theme to "Classic"

hrq-99 commented on 2025-11-15 21:16 (UTC) (edited on 2025-11-15 21:16 (UTC) by hrq-99)

After upgrading from chrome 140.0.7339.207-1 to 142.0.7444.162-1, all video playback shows heavy artifacting when HDR is enabled. SDR playback works normally.

Hardware: AMD ryzen 7700 & 7800XT Drivers: linux-firmware-amdgpu 20251111-1, mesa 1:25.2.7-1 WM: Hyprland 0.52.1-3

Rolling back to Chrome 140 fully resolves the issue, so this appears to be a regression related to HDR video handling.

kreucher commented on 2025-11-12 06:34 (UTC) (edited on 2025-11-12 06:35 (UTC) by kreucher)

@Acry i was getting the same GPU process exited unexpectedly: exit_code=139 error code here, and your suggestion of --disable-accelerated-video-decode indeed worked. but with that flag, Chrome seemed pretty slow/unstable on any page with video.

after much trial and error, i eventually fixed it by replacing libva-vdpau-driver with libva-nvidia-driver:

$ yay -S libva-nvidia-driver
(and told it to replace libva-vdpau-driver)

1 2 3 4 5 6 .. 164 Next › Last »