Package Details: google-chrome 148.0.7778.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: 2349
Popularity: 16.01
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2026-05-05 22:03 (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 .. 166 Next › Last »

yochananmarqos commented on 2026-04-08 20:02 (UTC)

@unklem: Add that to your ~/.config/chrome-flags.conf, that's what it's for:

--disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

unklem commented on 2026-04-08 18:43 (UTC)

Confirmed that MV2 extensions (e.g. uBlock Origin) still work in Chrome 147.0.7727.55

Add the following flags to your Exec line in ~/.local/share/applications/google-chrome.desktop or /usr/share/applications/google-chrome.desktop:

Exec=/usr/bin/google-chrome-stable %U --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

koshikas commented on 2026-04-08 14:38 (UTC) (edited on 2026-04-08 14:43 (UTC) by koshikas)

@mike.cloaked the pinned curl command to-date lists the latest GA (generally available) "google-chrome-stable" build correctly. it always has and still does.

what some confuses is what google releases as "Early Stable Release" which for the latest 147 was released on Wed, Mar 25, 2026. in googles words, "An Early Stable release is a version of Google Chrome released to a small percentage of users roughly one week before the general public release. It acts as a final testing phase to identify bugs or show-stopper issues before full deployment". you cans see when the timeline/roadmap for all chrome(ium) builds: https://chromiumdash.appspot.com/schedule

or-else there's is a remote chance you get cached curl responses. though very unlikely, it is still possible. check https://serverfault.com/questions/698077/does-curl-cache-requests

mike.cloaked commented on 2026-04-07 20:04 (UTC)

I mean that your command in the green block to use curl to get the Packages file and edit to extract the version works fine. But the link quoted to the Stable updates tag in the Release Block has out of date version listed - currently that link has "The Stable channel has been updated to 146.0.7680.177/178 for Windows/Mac and 146.0.7680.177 for Linux" which is not current. That was from 31st March and is a week old so doesn't have the current latest version listed.

gromit commented on 2026-04-07 19:42 (UTC)

@mike.cloaked what do you mean with your comment? I don't understand :D

mike.cloaked commented on 2026-04-07 19:35 (UTC) (edited on 2026-04-07 19:41 (UTC) by mike.cloaked)

The current latest version always seems to be correctly listed if you download the file https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages and check the lines starting (as current today)

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

Then the PKGBUILD can be updated to that version. So the pinned comment does look correct. But the stable updates tag is not usually up to date in the link.

schiele commented on 2026-03-29 05:16 (UTC)

@ZeNCUSioN Chrome for Testing is a different variation of Chrome than the regular package. The URL in the pinned comment is not a blog entry but the official repository meta data for the packages released for the Debian distribution. This package is repackaged then here to the Arch package. It might happen that Google releases Chrome for Testing in advance of the official release. In that sense the flaw is not in this package but in the chromedriver package that depends on this package instead of a corresponding chrome-for-testing package that needed to be created from this special variation. Alternatively, you need to make sure not to blindly update chromedriver to the very latest version available but to the version matching the latest official release as represented by this package here.

ZeNCUSioN commented on 2026-03-29 00:36 (UTC)

Are we sure the place to check for new versions of the Linux Desktop is the blog URL you list in your pinned comment? I ask because this link always seems to be a version behind the chromedriver making these two packages out of sync during an arch update.

There appears to be another page for stable releases at https://googlechromelabs.github.io/chrome-for-testing/ containing all the download links, including to the stable versions on all platforms that are in lockstep with chromedriver.

Thanks for all your work!

bubenkoff commented on 2026-02-16 15:28 (UTC)

Chrome 145.0.7632.75 (and all Chromium/Electron apps, including Firefox) crash immediately with free(): invalid size (SIGABRT) on glibc 2.43+r5+g856c426a7534-2 (CachyOS/Arch). Affects even --version. Workaround: install Chrome via Flatpak (flatpak install flathub com.google.Chrome) which bundles its own runtime. Symlink ~/.var/app/com.google.Chrome/config/google-chrome -> ~/.config/google-chrome to keep existing profiles. Use --password-store=kwallet5 on KDE for cookies.

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