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 .. 36 37 38 39 40 41 42 43 44 45 46 .. 157 Next › Last »

luzifer commented on 2019-04-05 00:03 (UTC)

@kronikpillow like @Det already commented and pinned: In those cases just flag the package outdated...

kronikpillow commented on 2019-04-04 23:55 (UTC)

==> Validating source files with sha512sums... google-chrome-stable_73.0.3683.86_amd64.deb ... FAILED eula_text.html ... Passed google-chrome-stable.sh ... Passed ==> ERROR: One or more files did not pass the validity check!

Det commented on 2019-04-02 01:07 (UTC)

@wingsuit, it's a binary pacakge, and hence mostly why. It was very much voted "trusted", and has +50% usage share in the world, but sure - not in the official repo. Just in Arch it's/used to be crashy, so Chromium, built for Arch, is better.

@jfcandidofilho, it was something like googling the "chrome deb/rpm repo" and prob also the URL in the /etc/cron.daily/ job that gets cleaned up from the package thru the line at the end of the PKGBUILD, which @luz also kept. I quit Arch & Linux, so my memory's a bit fading on these.

jsoy9pQbYVNu5nfU commented on 2019-03-30 15:30 (UTC)

Did ctrl+wheel zoom on websites stop working for anybody else along the way? It only works in PDF.js and other resource views now. Since I haven't used Chrome in a long time, I can't determine when the problem was introduced.

Perhaps it's just my configuration? kwin + x11 + synaptics driver.

Pryka commented on 2019-03-18 14:27 (UTC)

Is anyone have a strange download issue with v73.0.3683.75?

When I try to download a file bigger than ~100mb It just stops at 100% and nothing is happening, no matter how long I wait.

I tried in incognito, I restarted all Chrome settings, removed all extensions - nothing.

The only solution for me is to downgrade to v72.

Anyone?

wingsuit commented on 2019-03-13 09:51 (UTC)

"The popular web browser by Google (Stable Channel)"

I think we can all agree this software isn't trusted. It would be in the official repositories if it was.

jfcandidofilho commented on 2019-03-01 22:20 (UTC) (edited on 2019-03-01 22:25 (UTC) by jfcandidofilho)

@Det it's a bit unrelated to everything but where did you find those links for checksum and releases? I was googling about the checksum not working and if it weren't for you, I would fail to find a file with the checksum.

Of course, I could always direct myself towards the AUR but I sincerely couldn't find this info. I might just be blind...

Edit: I'm not well versed in packages functionality but we need an SHA512 and the file provides only SHA256, SHA1 and MD5sum. Is there a way to use MD5sum for that deb file only?

joelk commented on 2019-02-21 16:31 (UTC)

So, I uninstalled gnome-keyring and google-chrome-beta continued to work correctly. It loads and exits normally. Next I installed google-chrome-stable, tested to see that it worked correctly, then turned on Google Sync, and it crashed again just as it did before. I could get it to run by deleting .config/google-chrome but as soon as I turned on Sync again it crashed. Finally, I uninstalled libgnome-keyring (to do this I had to uninstall gksu, which I suppose I should have done anyway), started google-chrome-stable, turned on Sync and now it works correctly.

So to summarize, google-chrome seems to require that NEITHER gnome-keyring NOR libgnome-keyring be installed, or alternatively if libgnome-keyring is installed then gnome-keyring is needed temporarily when turning on Sync and it can subsequently be uninstalled. I have no explanation, but there it is.

leopicasso commented on 2019-02-21 09:26 (UTC)

Thanks for the information on the site. https://fivenights-at-freddys.com > Five Nights at Freddy's

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 157 Next › Last »