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.00
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 .. 71 72 73 74 75 76 77 78 79 80 81 .. 157 Next › Last »

resetko commented on 2016-03-10 21:16 (UTC) (edited on 2016-03-10 21:17 (UTC) by resetko)

After few last updates I've encountered problem with long shutdown/reboot time. After investigation I've found that problem comes only if I shutdown PC with chrome running. In shutdown log I've found timedout process in session-c2.scope: [ 423.510785] systemd[1]: session-c2.scope: Child 1337 belongs to session-c2.scope [ 451.565131] systemd[1]: systemd-logind.service: Got notification message from PID 486 (WATCHDOG=1) [ 452.065135] systemd-journald[207]: Sent WATCHDOG=1 notification. [ 452.065250] systemd[1]: systemd-journald.service: Got notification message from PID 207 (WATCHDOG=1) [ 511.565221] systemd[1]: session-c2.scope: Stopping timed out. Killing. [ 511.565398] systemd[1]: session-c2.scope changed stop-sigterm -> stop-sigkill [ 511.565563] systemd[1]: Received SIGCHLD from PID 945 (cat). [ 511.565582] systemd[1]: Child 945 (cat) died (code=killed, status=15/TERM) [ 511.565613] systemd[1]: session-c2.scope: Child 945 belongs to session-c2.scope And it was created by chrome, right? (raw http://pastebin.com/5VcgEjuh) systemd(1)-+-Thunar(692)-+-{gdbus}(863) ... |-xfce4-panel(690)-+-chrome(938)-+-cat(945) | | |-cat(946) | | |-chrome(989)-+-chrome(991) | | | |-{Chrome_ChildIOT}(993) | | | |-{SGI_video_sync}(1008) | | | |-{Watchdog}(992) | | | |-{WorkerPool/1005}(1005) | | | `-{handle-watcher-}(994) | | |-chrome-sandbox(948)---chrome(949)-+-chrome(954)-+-chrome(1001)-+-{Chrome_ChildIOT}(10+ | | | | | |-{CompositorTileW}(10+ | | | | | |-{CompositorTileW}(10+ | | | | | |-{CompositorTileW}(10+ | | | | | |-{CompositorTileW}(10+ ... This problem comes not always, but in ~85% of shutdowns with active chrome. How can I fix this? Can anyone confirm this?

Det commented on 2016-03-09 05:01 (UTC) (edited on 2019-04-05 02:27 (UTC) by Det)

✔ NOTE. If the sha512sums don't match, there's a new version. Simply flag the package.

You can check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates, or use:

$ curl -sL https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'

For new MD5: $ curl -sL https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | sed -n '35p'

Det commented on 2016-03-03 08:22 (UTC)

Kill it first.

justinnichols commented on 2016-03-03 00:40 (UTC)

After removing google-chrome manually and reinstalling via yaourt -S google-chrome, it acts as if it's obtained Google Chrome 49.0.2623.75, but after launching Chrome and viewing Help -> About Google Chrome, the version still shows 48.0.2564.109. Any thoughts?

Det commented on 2016-03-02 21:01 (UTC)

@xtrm0, "unmatching md5". No it isn't.

Det commented on 2016-03-02 20:53 (UTC) (edited on 2017-07-29 20:26 (UTC) by Det)

✔ OBS: 32-bit support for Google Chrome Stable Channel has been dropped as well. Either upgrade to 64-bit, or wait for phrakture to get hacked: - https://www.archlinux.org/news/phasing-out-i686-support/

<deleted-account> commented on 2016-03-02 20:42 (UTC)

@Det, sorry. That was stupid of me.

Det commented on 2016-03-02 20:40 (UTC)

But please don't flag it _after_ it's updated.

Det commented on 2016-03-02 20:36 (UTC)

Read the description, please.

<deleted-account> commented on 2016-03-02 20:35 (UTC)

Getting this- ==> Validating source files with md5sums... google-chrome-stable ... Passed eula_text.html ... Passed ==> Validating source_x86_64 files with md5sums... google-chrome-stable_48.0.2564.116_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build google-chrome.

« First ‹ Previous 1 .. 71 72 73 74 75 76 77 78 79 80 81 .. 157 Next › Last »