[ok] Chromium uses GNOME-keyring even though there is nothing to save

kalsan · 2016-09-05 08:35:10

Dear forum,

every time I reboot my computer, Chromium asks for my GNOME keyring password and does so until I give it. Seahorse shows that Chromium has an entry "Chromium Safe Storage" in my login keyring. This behaviour is new - it's only happening since one week ago. It's strange because I don't have anything confidential to be stored within Chrome, i.e. saving passwords is completely disabled.
Is anyone else experiencing this problem? I've been googling and there are lots of old threads about Ubuntu and co. but none of the solutions work for me: deleting the entry in Seahorse causes it to be recreated on Chromium's next start, and I don't want to disable / empty-password my GNOME keyring since I'm using it elsewhere.

Any help and discussion would be much appreciated.

Cheers,
Kalsan

Last edited by kalsan (2016-09-09 07:06:20)

WorMzy · 2016-09-05 09:44:22

This is probably chromium's password store detecting that you have gnome keyring installed/running and trying to use it, it's had the same annoying feature on KDE for a while. The solution is to change the Exec argument for your Chromium desktop file to: See below for a better solution that doesn't involve editing desktop files.

chromium --password-store=basic %U

See 'man chromium' for details about what this option does.

If gnome doesn't allow you to edit desktop files on-the-fly, manually copy /usr/share/applications/chromium.desktop to ~/.local/share/applications/ and modify it there manually.

Last edited by WorMzy (2016-09-05 12:45:32)

ooo · 2016-09-05 12:39:20

Instead of editing the chromium.desktop file, you can use ~/.config/chromium-flags.conf to pass command line options to chromium: https://wiki.archlinux.org/index.php/Ch … persistent

WorMzy · 2016-09-05 12:43:19

That's a much better solution, thanks, ooo.

kalsan · 2016-09-05 17:58:15

Thanks a lot for your replies! Sadly, none of the proposed solutions have any effect :-( The entry in seahorse is still automatically recreated when deleted, and Chromium asks for password upon reboot.
The steps I took were:
-> Equip all keyboard shortcuts for Chromium with the flag (no effect)
-> Creating the file ~/.config/chromium-flags.conf with the following content has no effect either:

# Persistent flags for Chromium
# https://wiki.archlinux.org/index.php/Chromium/Tips_and_tricks#Making_flags_persistent

--password-store=basic

WorMzy · 2016-09-05 18:25:36

If you navigate to chrome://version is '--password-store=basic' listed in the command line arguments?

EDIT: I can't get a link to that page to work. Just enter 'chrome://version' or 'about:version' in the URL field and press enter.

Last edited by WorMzy (2016-09-05 18:30:27)

loafer · 2016-09-05 19:45:45

They are ignored for me too (using .config/chromium-flags.conf). The command line argument is listed in chrome://version/ but I always get the password prompt upon opening Chromium.

kalsan · 2016-09-05 20:04:58

Yes, they are there. I'm getting exactly the same situation as loafer.

VDP76 · 2016-09-06 21:58:59

Hi everyone,
I am experiencing the same issues as kalsan (I'm using Chrome though).
Unfortunately none of the above proposed solution worked for me as well. I even tried to setup the PAM method described here with no luck. Deleting entries from seahorse and/or changing the "login" password to match the user password didn't help either.
Every suggestion would be very much appreciated...

glider · 2016-09-07 04:54:38

This bug is reported here: https://bugs.chromium.org/p/chromium/is … 20Modified

The new release is on the way. You can downgrade to v52 to get rid of it and wait for the new release.

Last edited by glider (2016-09-07 05:05:55)

kalsan · 2016-09-07 06:28:05

Thanks a lot for this comment! I hope the new release will fix the problem.

VDP76 · 2016-09-07 12:28:54

Thanks glider! Hopefully it will be fixed soon.

philo · 2016-09-08 19:06:42

When the window popped up asking for a password, I typed nothing (i.e. left the space blank) and just pressed the button 'OK' (or 'continue', I forgot the exact word).

I never saw the popup again.

EDIT - Running chromium version 53.0.2785.92-1, NOT goggle-chrome from AUR.

Last edited by philo (2016-09-09 10:19:18)

VDP76 · 2016-09-08 21:24:59

Good news everyone, the latest upgrade to google-chrome 53.0.2785.101-1 solved the issue.

kalsan · 2016-09-09 07:05:51

Same thing here :-)

loafer · 2016-09-09 13:03:37

It's OK for me with the latest version.

edit: replied to the wrong thread initially!

Last edited by loafer (2016-09-09 13:04:33)

infinf · 2016-09-15 20:29:33

Still having problems even with the latest version of chromium (and gnome3 i think).. every time i reboot i need to enter passwords on sites, that previously worked fine without it. It's annoying.
Tried chromium-flags.conf solution with no luck.
Downgrade to 52 version solved problem for me.

Marcin · 2016-09-24 08:03:13

Perhaps this is not a solution we were looking for, and please tell me if I am wrong.

For XFCE go to settings and startup applications. Then put a tick at GNOME keyring services. No annoying password prompts again.

Have a good day.

c00ter · 2016-09-25 01:33:21

I think this fix has been around for a while. I've had to use it in Debian and Arch in the distant (in Linux-years) past. Please forgive me if this does not provide a solution, diabetes affects my eye sight and I sometimes misread posts:

sudo mv /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon-old

sudo killall gnome-keyring-daemon

Regards

Arch Linux

#1 2016-09-05 08:35:10

[ok] Chromium uses GNOME-keyring even though there is nothing to save

#2 2016-09-05 09:44:22

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#3 2016-09-05 12:39:20

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#4 2016-09-05 12:43:19

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#5 2016-09-05 17:58:15

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#6 2016-09-05 18:25:36

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#7 2016-09-05 19:45:45

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#8 2016-09-05 20:04:58

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#9 2016-09-06 21:58:59

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#10 2016-09-07 04:54:38

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#11 2016-09-07 06:28:05

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#12 2016-09-07 12:28:54

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#13 2016-09-08 19:06:42

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#14 2016-09-08 21:24:59

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#15 2016-09-09 07:05:51

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#16 2016-09-09 13:03:37

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#17 2016-09-15 20:29:33

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#18 2016-09-24 08:03:13

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

#19 2016-09-25 01:33:21

Re: [ok] Chromium uses GNOME-keyring even though there is nothing to save

Board footer