Arch Linux User Repository

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.

@yizheng, this is not an issue with the package but rather with your setup since you need to have base-devel (which depends on fakeroot) installed as per https://wiki.archlinux.org/title/Arch_User_Repository#Getting_started

@abdulhakeem Compared to the past, the package also takes longer for me to compress. Lately yay it's updated, maybe it's from that?

• When I update to version 122.0.6261.94-1, there was an error.

Preparing...
Synchronizing package databases...
Cloning google-chrome build files...
Generating google-chrome information...
Checking google-chrome dependencies...
Resolving dependencies...
Checking inter-conflicts...

Building google-chrome...
==> ERROR: Cannot find the fakeroot binary.

• I fixed it on my local PC, just add 'fakeroot' into depends of PKGBUILD.

depends=(
    'alsa-lib'
    'fakeroot'
    'gtk3'
    'libcups'
    'libxss'
    'libxtst'
    'nss'
    'ttf-liberation'
    'xdg-utils'
)

• Hope this could help.

Latest update 122.0.6261.69-1 seems to be stuck on "Compressing package" for a long time. Usually takes only a few seconds at most. CPU is running near 100% so I think it's trying to compress, not sure what the issue might be.

CORRECTION: it seems to be an issue with yay and/or my system, not this package. Problem is occurring with other packages too. Disregard.

PS: should i remove my previous replies here then if it's not a pkg issue?

No you can leave them as-is, dont worry 🤗

@gromit, i switched network to my own hotspot instead of the business owned and now it works as intended, so probably they're doing https interception

@aki42 if i were you i would change network to something that you completely trust to not mess with https and try again, hope it helps!

PS: should i remove my previous replies here then if it's not a pkg issue?

I just downloaded and it works flawlessly.

@spindyckx, works on my machine .. Maybe something is messed up with your system time or the root CA store? But also I could imagine that dl.google.com is not the same depending on where you are connecting from, so maybe I'm not getting an error because I'm being connected to a different system.

In any case I think there's not much we could do here, maybe ask for help in debugging this in IRC, the forums and so on!

@gromit this is not only an issue with yay, when manually building the package i get the same error:

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

this seems to be an issue with dl.google.com as i get the same error when trying with a browser:

on firefox => Error code: SEC_ERROR_UNKNOWN_ISSUER

on chrome => ERR_CERT_AUTHORITY_INVALID

@aki, yes that one seems to be on you. Please note that generally AUR helpers are not supported, check out this for the official description: https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages

I've got the following error. Is it for me or a bug?

yay -S google-chrome                                                                                                                
AUR Explicit (1): google-chrome-120.0.6099.224-1
:: (0/1) Failed to download PKGBUILD: google-chrome
 -> error fetching google-chrome: error: invalid object 100644 3bc963edc436a8a786f5f3200af09ad9efda6601 for 'google-chrome-stable.sh'
Cannot save the current worktree state
fatal: Cannot autostash 
    context: exit status 128

Hello, i use prime nvidia drivers with dual gpu, discrete and integrated. As default i use the itegrate gpu but Google Chrome use the discrete gpu. How can i make Google Chrome to use the integrate gpu istead of the discrete?

Flags in chrome-flags.conf with quotes (--user-agent="Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.1)") are not applied correctly. Instead, multiple tabs are opened ("(compatible;", "msie", "6.0b;", "windows", ...).

Suggestions for dependency updates:

• kwallet should be kwallet5 for now
• Add plasma-browser-integration as optional for integration with KDE
• Is kdialog still required for KDE file dialogs? At least it's not the case for KDE Wayland session (which uses portal)

Outdated now. I have built new one. Here is the PKGBUILD

# Maintainer: Christian Heusel <christian@heusel.eu>
# Contributor: Knut Ahlers <knut at ahlers dot me>
# Contributor: Det <nimetonmaili g-mail>
# Contributor: t3ddy, Lex Rivera aka x-demon, ruario

# Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates
# or use: $ 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

pkgname=google-chrome
pkgver=118.0.5993.88
pkgrel=1
pkgdesc="The popular web browser by Google (Stable Channel)"
arch=('x86_64')
url="https://www.google.com/chrome"
license=('custom:chrome')
depends=(
    'alsa-lib'
    'gtk3'
    'libcups'
    'libxss'
    'libxtst'
    'nss'
    'ttf-liberation'
    'xdg-utils'
)
optdepends=(
    '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'
)
options=('!emptydirs' '!strip')
install=$pkgname.install
_channel=stable
source=("https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-${_channel}/google-chrome-${_channel}_${pkgver}-1_amd64.deb"
    'eula_text.html'
    "google-chrome-$_channel.sh")
sha512sums=('cae6a5cd8632ad350b41f4dfaf80449e6cf19d0b02816b9a1600f54b15df2adf5c4ded3792bfbe3855fa11a79ea256622f50180aa3c6779cedd75a55e7a6da9d'
            'a225555c06b7c32f9f2657004558e3f996c981481dbb0d3cd79b1d59fa3f05d591af88399422d3ab29d9446c103e98d567aeafe061d9550817ab6e7eb0498396'
            'de02b498a4b5b93e21622c8dba57befe795d733a04656be911cc38e28bfef0e20470450f44be523bbde8d4de28f79c10434846ca01fc2a2f4e67707b79332f94')

package() {
    bsdtar -xf data.tar.xz -C "$pkgdir/"

    # Launcher
    install -m755 google-chrome-$_channel.sh "$pkgdir"/usr/bin/google-chrome-$_channel

    # Icons
    for i in 16x16 24x24 32x32 48x48 64x64 128x128 256x256; do
        install -Dm644 "$pkgdir"/opt/google/chrome/product_logo_${i/x*/}.png \
            "$pkgdir"/usr/share/icons/hicolor/$i/apps/google-chrome.png
    done

    # License
    install -Dm644 eula_text.html "$pkgdir"/usr/share/licenses/google-chrome/eula_text.html
    install -Dm644 "$pkgdir"/opt/google/chrome/WidevineCdm/LICENSE \
        "$pkgdir"/usr/share/licenses/google-chrome-$_channel/WidevineCdm-LICENSE.txt

    # Fix the Chrome desktop entry
    sed -i \
        -e "/Exec=/i\StartupWMClass=Google-chrome" \
        -e "s/x-scheme-handler\/ftp;\?//g" \
        "$pkgdir"/usr/share/applications/google-chrome.desktop

    # Remove the Debian Cron job, duplicate product logos and menu directory
    rm -r \
        "$pkgdir"/etc/cron.daily/ \
        "$pkgdir"/opt/google/chrome/cron/ \
        "$pkgdir"/opt/google/chrome/product_logo_*.{png,xpm} \
        "$pkgdir"/usr/share/menu/
}

Here is the .SRCINFO

pkgbase = google-chrome
    pkgdesc = The popular web browser by Google (Stable Channel)
    pkgver = 118.0.5993.88
    pkgrel = 1
    url = https://www.google.com/chrome
    install = google-chrome.install
    arch = x86_64
    license = custom:chrome
    depends = alsa-lib
    depends = gtk3
    depends = libcups
    depends = libxss
    depends = libxtst
    depends = nss
    depends = ttf-liberation
    depends = xdg-utils
    optdepends = pipewire: WebRTC desktop sharing under Wayland
    optdepends = kdialog: for file dialogs in KDE
    optdepends = gnome-keyring: for storing passwords in GNOME keyring
    optdepends = kwallet: for storing passwords in KWallet
    options = !emptydirs
    options = !strip
    source = https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_118.0.5993.88-1_amd64.deb
    source = eula_text.html
    source = google-chrome-stable.sh
    sha512sums = cae6a5cd8632ad350b41f4dfaf80449e6cf19d0b02816b9a1600f54b15df2adf5c4ded3792bfbe3855fa11a79ea256622f50180aa3c6779cedd75a55e7a6da9d
    sha512sums = a225555c06b7c32f9f2657004558e3f996c981481dbb0d3cd79b1d59fa3f05d591af88399422d3ab29d9446c103e98d567aeafe061d9550817ab6e7eb0498396
    sha512sums = de02b498a4b5b93e21622c8dba57befe795d733a04656be911cc38e28bfef0e20470450f44be523bbde8d4de28f79c10434846ca01fc2a2f4e67707b79332f94

pkgname = google-chrome

117.0.5938.132-1 seems to have problems with mesa 23.2.1-1 (works fine with 23.1.8-1), on Intel irix graphics. Sample log, with repeated messages removed:

[5967:10:1004/104204.819729:ERROR:command_buffer_proxy_impl.cc(129)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[5769:5769:1004/104204.948403:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=139
[5967:10:1004/104205.573922:ERROR:command_buffer_proxy_impl.cc(321)] GPU state invalid after WaitForGetOff
setInRange.
[5967:10:1004/104205.573994:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error
------------------------
#version 100

precision highp float;
precision highp sampler2D;
uniform highp vec4 sk_RTAdjust;
uniform highp mat3 umatrix_S1_c0_c0;
attribute highp vec2 position;
attribute highp vec2 localCoord;
varying highp vec2 vTransformedCoords_4_S0;
void main() {
    gl_Position = vec4(position, 0.0, 1.0);
    {
        vTransformedCoords_4_S0 = (umatrix_S1_c0_c0 * vec3(localCoord, 1.0)).xy;
    }
    gl_Position = vec4(gl_Position.xy * sk_RTAdjust.xz + gl_Position.ww * sk_RTAdjust.yw, 0.0, gl_Position.w);
}

Apologies if this isn't the right place to report this; at the moment in the middle of a large project and can't determine whether chrome or mesa is at fault.

It might be a good idea to add NetworkManager and BlueZ as optional dependencies, as Chrom(e/ium) use their DBus APIs for geolocation and Bluetooth support respectively.

It seems that Google now has the correct latest version again, so presumably it was a temporary 'glitch'. Anyway this aur package is fine, and all seems well again.

@mike.cloaked The described method is still accurately describing this packages upstream. Strangely it seems like google has downgraded the version in the apt repo ... As I found no announcement nor complaints about major bugs or CVE's I just kept this package it as is, but if someone knows whats up please let me know! :)

Is there any other alternative way to query the current latest version direct from Google?

For a long time running the command: 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 has given the correct version for current upstream. But today it is giving an output as 116.0.5845.187 whereas the correct current stable version (including in this aur package) is 117.0.5938.62 - so I wonder if this is a temporary failure of Google to update dl.google.com, or if they decided not to update any more?

The Chrome version 117 appears to add support for HEVC and AV1 decode through VAAPI.

system-config-printer should at least be listed in optdepends, as outside of KDE it is the default dialog for managing printers, and some DEs such as XFCE have no fallback option. Otherwise, you get this error in the console: [7294:7319:0911/095606.965026:ERROR:printer_manager_dialog_linux.cc(100)] Failed to open printer manager dialog Source: https://chromium.googlesource.com/chromium/src/+/master/chrome/browser/printing/printer_manager_dialog_linux.cc

Chrome looks scary now. Almost like multiple screen tears. Degrading version also not working for me. This occurred after upgrading my arch to latest. Anybody facing the same?

I added -force-device-scale-factor=1.2 to my chrome-flags.conf and it looks good. am i right?

The latest update changed something with the DPI. Everything, including UI elements are massive now, even on my 1080p screen. Many pages I have to zoom out to around 80% to get what they're supposed to look like. I have no idea how to fix this.

Seems like vaapi hw video decode stopped working after updating to 116.0.5845.96-1. I've reverted to the previous version.

Once live captions is enabled, chrome tab CPU usage exceeds 500%, has anyone experienced this issue?

fixed after clear cache data and relaunch the chrome

@minime I think I managed to clear my issue by resetting chrome settings (Settings-Reset Settings) - no idea if this will cure your issue but it might be worth testing. But after the reset Chrome is no longer leaving a process in the background at 100%.

@dsyzling Just so you know, I think I have the same issue. Sometimes CPU utilization spikes up until chrome process gets killed. I wasn't able to pinpoint the exact scenario for a repro, it happens during google meet calls, during playing YT vids, sometimes even in idle. I run the latest arch kernels, proprietary nvidia drivers, i3wm. Machine is a PC, intel 6700k, 16gb ram. Hardware acceleration is on.

Has anyone else experienced 100% CPU utilisation with Chrome - even after closing the browser window I'm left with a chrome process at 100%? This started to occur with a new release a few months back. I've tried hardware acceleration flags and as far as I can see I have hardware decoding enabled. Machine is a Carbon X1 (gen 6). I can watch youtube videos without any issues but if I trigger a google search which yields youtube videos the cpu on one process goes to 100% and I have to manually kill the process from the command line.

I think trusted should be removed from the description

Can confirm the behavior described by dr1fter. Since the last update, google-chrome is unresponsive after resuming from standby.

Existing web pages are displayed properly but the GUI is completely unresponsive (change tab, add a tab, etc.).

I use Manjaro, linux-61 (6.1.31-2), gnome-shell (1:44.1-3) and linux61-nvidia (530.41.03-13).

I will try to find the logs next time it happens.

Dark mode is not working in last update

Did anything happen recently with forcing dark theme in chrome? Every time I start chrome now all of the pages are dark when following system theme. I do have a light/dark theme switcher script for my setup, but when I check the flags with chrom://version they are correctly passed. Any ideas?

Since recently (I do not track google-chrome versions), google-chrome will be frozen for ~1m after resuming from standby (systemctl suspend). I saw this behaviour for many months (started about one year ago); then about two months ago, the bug was gone (now it's there again).

The displayed webcontents are shown w/o any errors, however the GUI is fully unresponsive. If e.g. opening a new tab, this will happen after the application "thaws" after the mentioned ca. 1m. As a workaround, I tend to killall chrome (aka restart).

I run full system updates (pacman -Syu) daily, and update my AUR-packages about once a week. I use an NVIDIA graphics card w/ the non-free nvidia package.

hardware acceleration works again, thanks

@gromit It works OK now.

Thanks for fixing it that quickly.

@juangiordana thanks for the suggestion, could you check that comments are respected with the latest version I just pushed?

I modified your diff a bit so that only lines are ignored where the # is at the start of the line :)

/usr/bin/google-chrome-stable does not strip commented lines as suggested in the Arch Wiki. https://wiki.archlinux.org/title/Chromium#Making_flags_persistent

-CHROME_USER_FLAGS="$(cat $XDG_CONFIG_HOME/chrome-flags.conf)"
+CHROME_USER_FLAGS="$(grep -v '#' $XDG_CONFIG_HOME/chrome-flags.conf)"

Here is my changes in ~/.config/chrome-flags.conf to get working GPU acceleration again
- --use-gl=egl
+ --enable-gpu
Source: https://bugs.chromium.org/p/chromium/issues/detail?id=1412653

As @Kandscode says, passing --gtk-version=4 crashes Chrome. Is there any workaround for that? Without that parameter, FCITX (input method editor) does not work and I cannot type CJK text.

One possible upstream report regarding scaling in Wayland: https://bugs.chromium.org/p/chromium/issues/detail?id=1430500

I faced the same issue with almost no text rendering, @alki 's solution fixed it for me. Thanks alki!

P.S. this was a sign for me to switch to Vivaldi...

With chrome >= 113 I get the same wayland issue as Iyanmv already reported. I wanted to add that while it does scale incorrectly in any case, using it with KDE Plasma is particularly bad when the system window borders are enabled, because then the window is also displayed incorrectly, e.g. you can't click a link that is too far on the right side.

However, a quick search implies that it is very unlikely that the issue is caused in packaging. More likely, it's a bug either in chrome or in plasma-wayland. And since I experience the issue only with chrome and no other application, I guess it's a chrome bug.