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: 2237
Popularity: 7.89
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 .. 32 33 34 35 36 37 38 39 40 41 42 .. 157 Next › Last »

chrisu commented on 2019-11-23 15:57 (UTC)

I have managed to resolve the issue with version 78 by deleting the contents of ~/.config/google-chrome and restarting. It appears to be a chrome bug and not specific to Arch.

luzifer commented on 2019-11-16 14:34 (UTC)

@quite hmm I'm not sure this should be done. In the end the packages requiring chromium are expecting to find a Chromium browser while this package contains a Chrome browser. It doesn't listen on the same binary (and to prevent collisions it shouldn't do so) and it behaves differently… So I think I'll refrain from adding this as basically Chrome is not Chromium…

quite commented on 2019-11-16 09:58 (UTC) (edited on 2019-11-16 09:58 (UTC) by quite)

@luzifer, would you consider provides=('chromium')? Or is that mad? It would help pkgs that work with any chromium-based browser.

C_Schmidpeter commented on 2019-11-14 11:09 (UTC)

I tried to update from v72 to v78, but I got the following error message:

error: could not extract /opt/google/chrome/nacl_helper (Lzma library error: No progress is possible) error: problem occurred while installing google-chrome

chrisu commented on 2019-11-12 22:27 (UTC)

The update to chrome 78 has also broken it for me. Running chrome starts a number of chrome processes, but no window appears and it hangs. Neither --disable-gpu, nor --disable-software-rasterizer worked.

As NeonCloud noted, sudo google-chrome-stable --no-sandbox allows Chrome to load and display, but it's far from ideal.

Unfortunately, I am unable to downgrade to version 77 as only 78 is available to download from Google. I have installed Chromium, which at the time of install was version 77, and I am able to use that for now.

Det commented on 2019-11-07 12:31 (UTC)

@NeonCLoud, did you try clean profile or Chromium that's actually built for Arch?

NeonCloud commented on 2019-11-03 03:44 (UTC) (edited on 2019-11-03 05:15 (UTC) by NeonCloud)

@birdmun: Can confirm, worked fine until a full system update recently and now it's completely broken. I've tried reverting mesa and libglvnd back several months to no avail. With --disable-gpu provided, it silently hangs. With --disable-software-rasterizer as well, it then provides a different error entirely.

Curiously: sudo google-chrome-stable --no-sandbox allows Chrome to load, but it's quite unstable, not connected to my user account, and seriously far from ideal!

Edit: Ok, I downgraded to 77.0.3865.120, and it's working again. The jump to v78 seems to have been the commit that killed it.

birdmun commented on 2019-10-24 09:43 (UTC)

Am I the only person having errors trying to run the latest stable version of Chrome? [714745:714745:1024/054129.954039:ERROR:gl_context_glx.cc(187)] Failed to create GL context with glXCreateNewContext. [714745:714745:1024/054129.954270:ERROR:gpu_info_collector.cc(73)] gl::init::CreateGLContext failed [714745:714745:1024/054129.954289:ERROR:gpu_info_collector.cc(205)] Could not create context for info collection. [714745:714745:1024/054129.954326:ERROR:gpu_init.cc(66)] gpu::CollectGraphicsInfo failed. [714745:714745:1024/054129.964338:ERROR:viz_main_impl.cc(176)] Exiting GPU process due to errors during initialization

Worse yet the process continues to run in the background without offering anything to interact with.

alanmartinpmp commented on 2019-09-29 23:18 (UTC)

Can I simply just say what a comfort to find somebody that really knows what they're discussing on the internet You definitely understand how to bring an issue to light and make it important. More and more people really need to read this and understand this side of your story. It's surprising you're not more popular since you certainly possess the gift. https://www.papersjunction.co.uk

luzifer commented on 2019-09-09 09:35 (UTC) (edited on 2019-09-09 09:35 (UTC) by luzifer)

@tomrlopes When installing I've just used the package as is without changing anything (built in a freshly created Docker container). The CastLabs Demos are not working for me either. What does is the Bitmovin Player Demo [1]. On that page you also should see widevine EME detected and the video should be playable.

[1] https://bitmovin.com/demos/drm

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 157 Next › Last »