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 .. 85 86 87 88 89 90 91 92 93 94 95 .. 157 Next › Last »

Det commented on 2015-03-11 00:02 (UTC)

Well, you don't have to flag it _anymore_, I already updated it.

Det commented on 2015-03-10 23:27 (UTC)

Yep, it means there's a new version so the md5sum doesn't match anymore. You can use the *Flag package out-of-date* button in the future.

JetJaguarXP commented on 2015-03-10 23:20 (UTC)

Anyone else getting this? $ makepkg ==> Making package: google-chrome 41.0.2272.76-1 (Tue Mar 10 16:16:04 MST 2015) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found eula_text.html -> Downloading google-chrome-stable_41.0.2272.76_amd64.deb... ==> Validating source files with md5sums... google-chrome-stable_41.0.2272.76_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!

abhisit commented on 2015-03-05 04:33 (UTC)

Thanks a lot.

cellisten commented on 2015-03-03 19:58 (UTC)

New md5sum and also changed from data.tar.lzma to data.tar.xz

Det commented on 2015-03-01 16:00 (UTC)

@shibumi, why?

<deleted-account> commented on 2015-02-28 09:35 (UTC)

And I disable all extensions :-/

<deleted-account> commented on 2015-02-28 09:35 (UTC)

No I dont actually. I made sure to disable all the things that I suspected would keep a zombie process alive.

Det commented on 2015-02-28 08:51 (UTC)

It might be some extension or app that's causing it. Do you have "menu → Settings → Continue running background apps when Google Chrome is closed" on (default)?

<deleted-account> commented on 2015-02-27 23:32 (UTC)

Ahh I see that. Unfortunately that didn't help. I think I know what is happening though. Occasionally when closing chrome, a process will linger. Not every time, but about 1/3 times. If I open a new chrome instance before that previous process is closed, I throw database profile errors, as the database is still locked as long as that lingering process remains open. I have found that ending all the chrome processes one by one will allow me to open chrome without an issue, and there is always one that is stubborn to close and forces me to kill the process. As to why a process lingers open, I have no idea.

« First ‹ Previous 1 .. 85 86 87 88 89 90 91 92 93 94 95 .. 157 Next › Last »