Package Details: google-chrome 130.0.6723.116-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: 2243
Popularity: 7.15
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-05 19:02 (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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 157 Next › Last »

Kandscode commented on 2023-05-03 15:40 (UTC)

Oh, I used the flag --gtk-version=4, which causes Chrome to crash.

iyanmv commented on 2023-05-03 15:30 (UTC)

Anyone having issues with the latest version on Wayland? All app is wrongly scaled with --ozone-platform-hint=auto in ~/.config/chrome-flags.conf

Kandscode commented on 2023-05-03 15:22 (UTC)

@gromit Oh, I reinstalled Chrome after deleting all Chrome related files and now it's working fine again, sorry to bother.

gromit commented on 2023-05-03 14:55 (UTC)

@Kandscode you could try a few things:

  • see if the problem also exists for google-chrome-{beta,unstable} if you didnt specify any custom flags this might indicate there is a bug with chrome itself
  • create the path in the error message /home/kands/.config/google-chrome/Crash Reports/attachments/ and see if the error is then successfully written out there

Kandscode commented on 2023-05-03 14:47 (UTC)

@gromit When I start chrome in the terminal, the following error message will appear, and I have not used any flags.

$ google-chrome-stable 

[0503/224505.364103:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0503/224505.377502:ERROR:directory_reader_posix.cc(42)] opendir /home/kands/.config/google-chrome/Crash Reports/attachments/7ede611b-8e62-4d29-a7e2-0086571ee395: No such file or directory (2)
Segmentation fault (core dumped)

gromit commented on 2023-05-03 07:42 (UTC)

@Kandscode did you put custom flags in "~/.config/chrome-flags.conf" by any chance? In any case you could start chrome from a terminal and see if an error pops up :)

Kandscode commented on 2023-05-03 04:46 (UTC)

Chrome version 113.0.5672.63-1 does not start on my computer for unknown reasons.

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.

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