Package Details: google-chrome 126.0.6478.114-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: 2227
Popularity: 6.35
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-06-18 20: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 .. 156 Next › Last »

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.

    kobe-koto commented on 2022-10-06 10:12 (UTC) (edited on 2022-10-06 10:13 (UTC) by kobe-koto)

    I have installed chrome 106.0.5249.103-1 on manjaro, but dark mode doesn't work in settings (chrome://settings/) (works fine in other sites that support dark mode)?

    I have added --force-dark-mode to the arguments.

    What should I do to fix this problem?

    visious commented on 2022-10-05 09:50 (UTC)

    Hi, I'm getting this chrome_crashpad_handler in google-chrome over and over again in Task Manager Xfce:

    /usr/share/skypeforlinux/chrome_crashpad_handler --monitor-self-annotation=ptype=crashpad-handler --no-rate-limit --database=/home/visious/.config/skypeforlinux/Crashpad --url=appcenter://generic?aid=70b7a841-531e-4f9a-9b55-ff40f9d0fb67&iid=1edba44e-484c-407d-c344-86311a28eed0&uid=1edba44e-484c-407d-c344-86311a28eed0<##>aria://?_event=main_crashed&_token=a173030604a34bdcbf21ca59134c7430-2a34e3b5-60e1-4a11-ad6d-2e9eac9ac07c-6614&CrashType=native_crash&DeviceInfo.Id=1edba44e484c07dc34486311a28eed02&DeviceInfo.OsName=Linux&DeviceInfo.OsVersion=5.19.12-arch1-1&Platform_Id=1431&Platform_Uiversion=1431/8.88.0.401/ --annotation=_companyName=Skype --annotation=_productName=skypeforlinux --annotation=_version=8.88.0.401 --annotation=lsb-release=Arch Linux --annotation=plat=Linux --annotation=prod=Electron --annotation=ver=19.0.9 --initial-client-fd=42 --shared-client-connection

    $ pacman -Qi google-chrome Name : google-chrome Version : 106.0.5249.61-1 Description : The popular and trusted web browser by Google (Stable Channel) Architecture : x86_64 URL : https://www.google.com/chrome Licenses : custom:chrome Groups : None Provides : None Depends On : alsa-lib gtk3 libcups libxss libxtst nss ttf-liberation xdg-utils Optional Deps : pipewire: WebRTC desktop sharing under Wayland kdialog: for file dialogs in KDE gnome-keyring: for storing passwords in GNOME keyring kwallet: for storing passwords in KWallet Required By : None Optional For : None Conflicts With : None Replaces : None Installed Size : 286.14 MiB Packager : Unknown Packager Build Date : Thu 29 Sep 2022 03:08:51 PM EEST Install Date : Thu 29 Sep 2022 03:09:22 PM EEST Install Reason : Explicitly installed Install Script : Yes Validated By : None

    PS: skypeforlinux is working well, google-chrome crashes.

    elizabethdev commented on 2022-09-10 20:48 (UTC) (edited on 2022-09-10 20:54 (UTC) by elizabethdev)

    Hi.

    Somehow, upgrading this from 104.0.5112.79-1 to 105.0.5195.102-1 breaks the ability to write special characters (ñ, ç, á, à...) in textboxes when using Ozone/Wayland.

    This has been reported at https://bugs.chromium.org/p/chromium/issues/detail?id=1360070, I'm just posting this so anyone who comes here with the same problem knows this is the cause.

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