Package Details: google-chrome 131.0.6778.85-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: 2247
Popularity: 9.36
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-19 19:19 (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 2 3 4 5 6 7 8 .. 157 Next › Last »

gromit commented on 2024-04-24 09:37 (UTC)

@bassadin are you on Wayland?

bassadin commented on 2024-04-24 06:32 (UTC)

Since a few updates, my Chrome windows are invisible at launch until I blindly type "about://restart" into a new tab. Is this the same issue with the ozone platform that you are talking about?

hexchain commented on 2024-04-23 11:53 (UTC)

Would you please consider putting up a google-chrome-debug PKGBUILD? Debug symbol files for Chrome are public and can be downloaded, see: https://issues.chromium.org/issues/41141025#comment44.

fthiery commented on 2024-04-23 07:37 (UTC)

For me google-chrome-beta (125.0.6422.4) shows up normally and as wayland surface (without any switch/config needed), maybe next release will fix this white screen issue ...

urparvezali commented on 2024-04-23 04:51 (UTC)

facing the ozone platform = wayland issue. the browser windows do not show.

Edu4rdSHL commented on 2024-04-21 01:38 (UTC)

@ciupenhauer, honestly I think that updating + adding the --ozone-platform=wayland option to the launch options is the best option.

ciupenhauer commented on 2024-04-19 20:06 (UTC)

@Edu4rdSHL thanks for all the links. Doesn't look like this will get solved anytime soon, it's been reported since march. Downgrading seems the best option

johnsm1th commented on 2024-04-17 08:11 (UTC)

need to add CHROME_WRAPPER environment variable so that the PWA application startup icon gets the correct exec path.

export CHROME_WRAPPER="`readlink -f "$0"`"

Edu4rdSHL commented on 2024-04-17 03:18 (UTC) (edited on 2024-04-17 03:24 (UTC) by Edu4rdSHL)

Avoid updating to version 124 if you use Wayland. It doesn't work there since the beta. https://aur.archlinux.org/packages/google-chrome-beta#comment-963012

Edit: here's the upstream report: https://issues.chromium.org/issues/329678163

It only seems to affect if you have set the option from chrome://flags/, if you manually run google-chrome-stable --ozone-platform=wayland from the command line, it works.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 157 Next › Last »