Package Details: google-chrome 136.0.7103.113-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: 2276
Popularity: 11.35
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-05-14 19:12 (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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 32 Next › Last »

ABOhiccups commented on 2018-06-18 08:45 (UTC)

Google Chrome won't open after installing Plymouth with arch-plymouthize when I turn on the computer.

Something has to do with /etc/fonts/fonts.conf Error.

topcat commented on 2018-06-12 18:28 (UTC)

md5sum failing as Google have updated to version 67.0.3396.87...

Det commented on 2018-06-02 10:19 (UTC) (edited on 2018-06-02 10:24 (UTC) by Det)

Well I've no idea what link u went into, but the blog (and direct link) are up to date.

You can always verify the version that gets pulled in directly with the repo data command, since the source link doesn't change.

E: The 66.0.3359.203 from May 31st, not 13th is for Chrome OS.

Det commented on 2018-05-29 19:47 (UTC)

Your package google-chrome [1] has been flagged out-of-date by newfell0w [2]:

release 66.0.3359.181 is current

Already updated.

Det commented on 2018-05-21 04:31 (UTC)

dnl_tp flagged google-chrome out-of-date on 2018-05-21 for the following reason:

google chrome asks to be updated... i guess it is outdated...

Nope.. see the pinned comment.

Det commented on 2018-05-15 19:01 (UTC) (edited on 2018-05-15 19:01 (UTC) by Det)

Your package google-chrome [1] has been flagged out-of-date by adherr [2]:

==> Validating source files with md5sums...

google-chrome-stable_66.0.3359.170_amd64.deb ... FAILED

It's already updated, mate.

Det commented on 2018-05-15 16:47 (UTC)

Nice spam from 2 weeks ago, didn't notice that.

Good thing they collapse now. <3

FXCNN commented on 2018-05-02 16:43 (UTC)

problemas al ejecutar google-chrome

<hr>

google-chrome-stable Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "its:rules" Fontconfig warning: "/etc/fonts/fonts.conf", line 6: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'translate' Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'selector' Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'version' Fontconfig warning: "/etc/fonts/fonts.conf", line 9: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/30-metric-aliases.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/40-nonlatin.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/45-generic.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/49-sansserif.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/50-user.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/51-local.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/60-generic.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/60-latin.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/65-fonts-persian.conf", line 34: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/65-fonts-persian.conf", line 35: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 35: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 35: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 36: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/65-fonts-persian.conf", line 36: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/65-nonlatin.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/69-unifont.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/69-unifont.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/69-unifont.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/80-delicious.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/80-delicious.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/80-delicious.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/90-synthetic.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/90-synthetic.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 6: invalid attribute 'version' Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf

huiser commented on 2018-04-28 16:01 (UTC)

AUR Packages (1) google-chrome-66.0.3359.139-1

:: Proceed with installation? [Y/n] y :: Retrieving package(s)... :: Checking google-chrome integrity... ==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.

==> ERROR: An unknown error has occurred. Exiting... :: failed to verify google-chrome integrity

ohmysql commented on 2018-04-27 20:08 (UTC)

I get this message in build. I googled and couldn't see if it was bad :

==> Verifying database signature... ==> WARNING: No existing signature found, skipping verification. ==> Extracting database to a temporary location... ==> Verifying database signature... ==> WARNING: No existing signature found, skipping verification. ==> Extracting database to a temporary location... ==> Adding package 'google-chrome-66.0.3359.139-1-x86_64.pkg.tar.xz' -> Computing checksums... -> Removing existing entry 'google-chrome-66.0.3359.117-1'... -> Creating 'desc' db entry... -> Creating 'files' db entry...

foutrelis commented on 2018-04-19 17:32 (UTC)

@Pryka: Probably the same thing that happened to me: Chrome lost the random password it stores in the keyring as "Chrome Safe Storage", which it uses to encrypt cookies. After that is lost, any new cookies created don't overwrite their old counterparts and thus we end up with duplicate cookies.

The cookie handling behavior has changed in Chrome 66 and duplicate cookies should no longer be created (it was a rare issue in the first place). There might still be some problematic behavior though, as I noted in the upstream bug. It's also still the case that losing "Chrome Safe Storage" will make all cookies encrypted with it unreadable.

Pryka commented on 2018-04-19 16:58 (UTC)

@foutrelis Yeah, bunch of dupes.

But I don't understand now... Why creating a new profile fixed that on my machine? I jumped back and fort from 64 to 66 just to check it. And I'm not losing anything now. Chrome stays log in on sites an google account after each update.

foutrelis commented on 2018-04-19 16:48 (UTC)

@Pryka: If you have a backup of your Chrome 65 profile, you can run this query on its Cookies database: https://crbug.com/800414#c26

If it returns anything other than 0, then duplicate cookies was the reason you lost your cookies after upgrading to Chrome 66.

Pryka commented on 2018-04-19 16:45 (UTC) (edited on 2018-04-19 16:45 (UTC) by Pryka)

@foutrelis

Could be. But it seams to work normal after creating clean profile files. At least for now. Have to wait for the v67 to be sure.

foutrelis commented on 2018-04-19 16:37 (UTC)

@Pryke: Cookie loss after upgrading to M66 can be due to https://crbug.com/800414#c37

@Det: You can remove gconf from the dependencies. It's not been needed since Chrome 65 I believe.

Pryka commented on 2018-04-19 16:26 (UTC)

@Det:

Couldn't reproduce it in Chromium 65 and 66.

Apparently it was some kind of corruption of my Google-Chrome profile. Created new one. Downgraded/Updated(65<-->66) and everything is working fine now(with sync on and off). Thank You.

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

@Det Thank you for the interest.

I'll do this tomorrow, anyway I will get back to You and post results.

Det commented on 2018-04-18 19:37 (UTC)

It'd be interesting, if you could test this with Chromium also: https://archive.archlinux.org/packages/c/chromium/

And if can't reproduce, then with clean profile on Chrome (non-synced) (see /var/cache/pacman/pkg or e.g. https://dl.google.com/linux/deb/pool/main/g/google-chrome-stable/google-chrome-stable_65.0.3325.181-1_amd64.deb).

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.

Det commented on 2018-02-25 12:01 (UTC)

Wow, yes it is.

That's super sad and annoying.

TiD91 commented on 2018-02-25 10:19 (UTC)

Ok. I just saw pacaur is unmantained... Arch is too fast for me sometimes :)

Det commented on 2018-02-25 10:18 (UTC)

clear ~/.cache/pacaur

TiD91 commented on 2018-02-25 10:17 (UTC)

Guys, If I try to install this with pacaur, I get: :: Installing google-chrome package(s)... :: google-chrome package(s) failed to install. :: ensure package version does not mismatch between .SRCINFO and PKGBUILD :: ensure package name has a VCS suffix if this is a devel package

But installing it manually works ok. Any idea how to fix this?

Det commented on 2018-02-23 18:13 (UTC)

Manjaro? You'll be doing another perfect update in a minute.

Jorre commented on 2018-02-23 16:22 (UTC)

I also ran into the md5 checksum error: ==> Validating source files with md5sums... google-chrome-stable_64.0.3282.167_amd64.deb ... FAILED

I decided to run yaourt with skipping validity checks: yaourt --m-arg "--skipchecksums --skippgpcheck" -Syua

This works fine for me and chrome updated perfectly.

Det commented on 2018-02-06 12:46 (UTC)

+1

I just use pkill.

beoldhin commented on 2018-02-06 09:51 (UTC)

Added a Github page describing the shutdown problems observed with chrome and chromium (includes fix to "Chrome didn't shutdown correctly"): https://github.com/beoldhin/killgroup

rakotomandimby commented on 2018-02-05 19:05 (UTC)

You're right, the synchronization screws it all. If I dont sync, it restarts all right. If I ever sign in, it syncs then I cant relaunch it unless I remove config.

Workaround it to stay signed out for the moment. But that's weird.

I'll configure synchronization one by one and tell.

Det commented on 2018-02-05 18:59 (UTC)

Probably you're not closing it right. Or it happens after syncing extensions, etc.

I'd go step by step.

rakotomandimby commented on 2018-02-05 18:44 (UTC)

But it only works 1 launch after the remove of the directory: if I close Chrome and relaunch again, it fails.

rakotomandimby commented on 2018-02-05 18:41 (UTC)

"rm -rf ~/.config/google-chrome ; rm -rf ~/.cache/google-chrome" made it works for me...

Det commented on 2018-02-03 13:21 (UTC) (edited on 2018-02-03 13:22 (UTC) by Det)

What else is there besides the sums?

MarcinWieczorek commented on 2018-02-03 09:40 (UTC)

Please retire md5 and switch to sha256 at least for checksums :)

Det commented on 2018-02-02 03:13 (UTC) (edited on 2018-02-02 03:13 (UTC) by Det)

@belochub: for the differences between those, see: https://support.google.com/chromebook/answer/1086915?hl=en

The other two are: https://aur.archlinux.org/packages/google-chrome-beta/, https://aur.archlinux.org/packages/google-chrome-dev/

fuan_k commented on 2018-01-23 19:16 (UTC)

@clepi: from my experience, it's Chrome populating its History information or something. You can see it read a lot of things from disk and load it in memory. Can be databases generated by some extensions too, mostly related to history and cache usually.

ciepi commented on 2018-01-21 15:26 (UTC)

I have cleared ~/.config/google-chrome & ~/.cache/google-chrome but it still won't work.

Det commented on 2018-01-21 14:52 (UTC)

Went through the normal troubleshooting of renaming ~/.config/xxx/ & ~/.cache/xxx/, and looking at the terminal output?

ciepi commented on 2018-01-21 14:48 (UTC)

When I open chrome (or even chromium) I cannot use it - it's not responsive (can't even type anything in search bar). It've been installed without errors. Does anyone have the same issue? Moreover it works perfectly fine on my laptop, but it won't on pc.

beoldhin commented on 2018-01-17 08:51 (UTC) (edited on 2018-01-18 21:25 (UTC) by beoldhin)

I get the message "Chrome didn't shutdown correctly" always when I start Chrome after restarting the computer. I found out that Chrome leaves some processes running even after the browser is closed. Closing these processes with "killall chrome" before restart fixes this problem. The default signal sent by killall is "sigterm" but systemd probably sends something "faster" to the processes during shutdown, leaving them in unclean state.

Update: grepping chrome process tree root process with "pgrep -o chrome" and then killing that process + waiting for the directory to disappear from proc works better than "killall" that sometimes works, sometimes doesn't.

zerophase: "Is anyone else having issues with Chrome refusing to launch lately?". Yes. I just moved from chromium to chrome in one system with Cinnamon and other with Gnome 3. Launching chrome in Cinnamon doesn't work (hangs forever) but in Gnome 3 it does so there does seem to be that almost required dependency to gnome-keyring.