Package Details: google-chrome 137.0.7151.68-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: 2281
Popularity: 11.36
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-06-03 13:24 (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 .. 48 49 50 51 52 53 54 55 56 57 58 .. 159 Next › Last »

Pryka commented on 2018-04-18 18:51 (UTC) (edited on 2018-04-18 19:01 (UTC) by Pryka)

Hello!

Probably since v64 every time I perform chrome update to next major version like 64-->65 or now to 66. Chrome is losing all my sessions and I need to relog to almost every single site I use. Not ground breaking but annoying.

Anyone noticed similar behaviour?

PS. This bug or whatever it is do not occur when update are performed is in the same line, like: 65.0.3325.162 --> 65.0.3325.181.

EDIT: Did a little digging and it's looks that I have lost a whole lot of cookies after update. So this was probably the culprit in the previous ones(updates). Still no idea why this is happening.

Det commented on 2018-04-18 16:39 (UTC)

Oh my god, don't post a comment about it.

glowingsword commented on 2018-04-18 13:50 (UTC)

Please, update the PKGBUILD, the release to

pkgver=66.0.3359.117

and md5sums to

md5sums=('c979c8fac57b9f78de0b899f1b09ce39' 'd50d8f0a6940791eabc41c4f64e6a3cf' '99fa93d5e7fb5d622cef0f9621f3ffa3')

zerophase commented on 2018-04-17 00:09 (UTC)

@fuan_k Thanks. I just needed to confirm my overclocked ram wasn't causing the segfault.

fuan_k commented on 2018-04-16 23:39 (UTC)

@zerophase: yes, got the same segfault with 390.48 drivers, downgraded to 387.34.

zerophase commented on 2018-04-14 16:53 (UTC)

Has anyone else gotten this segfault?

[Sat Apr 14 11:41:35 2018] chrome[6358]: segfault at 4 ip 00007ff51a018967 sp 00007fff116c9388 error 6 in libnvidia-glcore.so.390.48[7ff518df5000+141e000]

Det commented on 2018-04-02 14:17 (UTC)

Smoerrebroed flagged google-chrome out-of-date on 2018-04-02 for the following reason:

New release is out!

No there isn't.

v8areu commented on 2018-03-26 00:59 (UTC) (edited on 2018-03-26 01:00 (UTC) by v8areu)

So for now, we cannot log in and sync the extension etc for it to be run properly? Because (as others have mentioned below) if I ever log in + sync, google chrome won't start.

I don't actually need this to be synced because I mainly use chromium and I want to use chrome for testing purpose. But this is weird.

« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 159 Next › Last »