Package Details: google-chrome 129.0.6668.58-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: 2236
Popularity: 7.34
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 157 Next › Last »

blackhole commented on 2023-01-12 08:46 (UTC)

I cannot start google-chrome

From command line I see the error "dri3 extension not supported"

Browser window flashes up ant then closes.

I have already tried to delete google configuration and start it with the option --disable-gpu.

god commented on 2023-01-12 05:31 (UTC)

How about changing the desktop file like below. Without that option, if I enable Wayland (about:flags, Preferred Ozone platform = Auto), I cannot type foreign languages using Fcitx5. If I manually modify the desktop file, when Chrome gets updated, the change gets lost. Are there any downsides of that option? I don't know exactly, but even if that option is specified, if GTK 4 is not available, won't it fall back to GTK 3 anyway?

Exec=/usr/bin/google-chrome-stable --gtk-version=4 %U

toropisco commented on 2023-01-08 14:48 (UTC)

@luzifer and BTW, https://bugs.chromium.org/p/chromium/issues/detail?id=409922 is WONTFIX because fontconfig does what it is supposed to do. https://bugs.archlinux.org/task/41795 is TBH, spurious.

toropisco commented on 2023-01-08 13:41 (UTC)

@luzifer, you don't need to hard code it. Fontconfig work is, among other things, to do font substitition and Google Chrome works perfectly fine with the ChromeOS fonts (as it has been my experience with my Chromebook).

luzifer commented on 2023-01-07 21:52 (UTC)

@toropisco as the Chromium source code (as also reflected in the Chromium package) strongly depends on the liberation font while almost no mentions of the fonts contained in the croscore package are found, liberation will stay a dependency of this package.

toropisco commented on 2023-01-07 21:32 (UTC)

Hi, would you mind changing the ttf-liberation dependency in this package and the other beta and dev packages to the ttf-font meta-package or, at the very least, to ttf-croscore? As it is now, the ttf-croscore package (the default fonts in Google's ChromeOS) is in the extra repository while ttf-liberation has been demoted to community (it hasn't been updated in some 10 years now). Ideally, ttf-font is the best for choice reasons, but ttf-croscore is the best for consistency and coherency; it is based on Liberation and has been actively maintained till today.

mikesco3 commented on 2022-11-25 13:59 (UTC) (edited on 2022-11-25 14:08 (UTC) by mikesco3)

I'm getting: Failed to generate google-chrome information While trying to update with Manjaro
Never, mind ...
I found the answer below:
For anyone else who is experiencing this issue:

  • Open **Pamac** (the app than runs your updates),
  • click three lines at top right,
  • click "preferences",
  • click "third party",
  • then click "clean" at the bottom,
  • Re-run the update
    this cleans the build directory and fixes the problem, your Chrome will now update with no issues.

    • mare2k commented on 2022-10-26 08:48 (UTC)

    Hi Google-chrome dark-mode:

    1. "chrome://flags/"
    2. search "Auto Dark Mode for Web Contents"
    3. mark field "Enabled" or "chrome://flags/#enable-force-dark" ENTER

    psypherium commented on 2022-10-09 08:32 (UTC)

    For anyone else who is experiencing "Failed to generate google-chrome information" issue: Open Pamac, click three lines at top right, click "preferences", click "third party", then click "clean" at the bottom, this cleans the build directory and fixes the problem, your Chrome will now update with no issues. There's probably a terminal command for this also.

    « First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 157 Next › Last »