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)?
Search Criteria
Package Details: google-chrome 131.0.6778.85-1
Package Actions
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: | 2246 |
Popularity: | 8.78 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-19 19:19 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet (kwallet-gitAUR) (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (40)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-extension-adnauseam (optional)
- chromium-extension-autoscroll (optional)
- chromium-extension-plasma-integration (optional)
- chromium-extension-runet-censorship-bypass (optional)
- chromium-material-icons-for-github-bin (optional)
- chromium-vencord (optional)
- chromium-vencord-bin (optional)
- chromium-vencord-git (optional)
- dedao-dl-bin (optional)
- endpoint-verification-chrome
- endpoint-verification-minimal
- ff2mpv-go-git (optional)
- ff2mpv-rust (optional)
- hub-kids (optional)
- hub-young (optional)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 86 87 88 89 90 91 92 93 94 95 96 .. 157 Next › Last »
Det commented on 2015-02-28 08:51 (UTC)
<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.
Det commented on 2015-02-27 23:20 (UTC)
You know, "menu → Settings → Manage search engines...", which are saved in the 'Web Data' database.
<deleted-account> commented on 2015-02-27 23:18 (UTC)
What do you mean by one of my search engines?
Det commented on 2015-02-27 23:08 (UTC)
If it's on four computers with different settings, then that's systemic. Maybe some extension is screwing it up, or one of your search engines has a corrupt configuration, which is getting synced to all the rest of them.
<deleted-account> commented on 2015-02-27 23:06 (UTC)
Nvm, that was not the fix to my problem. If I close and reopen chrome in too close of a succession I get a "profile could not be loaded" error message. Looking in system-monitor shows a chrome process remaining open even though all windows are close (and I have the stay open option turned off). I think it has something to do with a local sql database, as deleting 'web-data' in the /config/google-chrome/default will fix the issue temporarily. And it happens on four of my computers with completely different architecture.
Det commented on 2015-02-27 23:01 (UTC)
Shouldn't you clear your cache then?
<deleted-account> commented on 2015-02-27 23:00 (UTC)
I kept having my profile fail to load nearly every time I opened Chrome, however appending "--disk-cache-dir=/tmp/cache" to the end of the exec lines in the .desktop file has helped tremendously. Is there any way to do this globally so that way I do not have to redo it each update?
Det commented on 2015-02-22 16:26 (UTC)
AJSlye, reason?
WorMzy commented on 2015-02-19 16:50 (UTC)
40.0.2214.115 just out: http://googlechromereleases.blogspot.co.uk/
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:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.