You are not logged in.
Getting rid of some to-come questions beforehand:
1) gnome-keyring is setup properly with a password, network-manager and other apps are using it just fine.
2) I don't intend to leave access to chrome at all on it with or without a password.
3) I did read https://bbs.archlinux.org/viewtopic.php?id=238377 , and did some research (stack overflow, etc), the solutions as far as I know amount to either : disable gnome-keyring, leave a blank password, or remove chrome completely.
I use mainly firefox, and I did setup different profiles but sometimes I do want to use chrome for specific tasks.
So : is there a way to have chrome (by editing it's files) to stop asking me to unlock the keyring , without me having to either unlock the keyring and letting it in, or leaving it without a password which would be pointless since the passwords as well would be stored in blank
Hopefully this will get us all right to the point and some chromium kung-fu master can shed some light into this matter.
Last edited by r0b0t (2019-04-28 00:42:48)
Offline
Not tested this but https://bugs.chromium.org/p/chromium/is … ?id=571003 indicates chrome 74 should prefer the LoginDB.
Edit:
Ah missed:
https://bugs.chromium.org/p/chromium/is … ?id=950269 so it is then indirectly needed
https://bugs.chromium.org/p/chromium/is … ?id=660005
Last edited by loqs (2019-04-28 00:41:06)
Offline
I am actually using
pacman -Q chromium
chromium 74.0.3729.108-1so in theory chromium's drilling should be over, but it still keep drilling gcr-prompter for a go with gnome-keyring.
In any case thanks allot for the link, reading the comments I did find out something really interesting and gave it a try, guess what. Now the drilling is over and the problem is solved.
For those interested:
root:/usr/share/applications # cat chromium.desktop | grep -i Exec
Exec=/usr/bin/chromium --password-store=basic %USo, just add --password-store=basic on the application's shortcut and you'r done.
Offline
So, just add --password-store=basic on the application's shortcut and you'r done.
That's not a good way to do it. At the very least it will get clobbered each time the package updates. The Arch solution is Making flags persistent.
Last edited by bulletmark (2019-04-28 03:11:52)
Offline
r0b0t wrote:So, just add --password-store=basic on the application's shortcut and you'r done.
That's not a good way to do it. At the very least it will get clobbered each time the package updates. The Arch solution is Making flags persistent.
Thanks, added it now , it works well.
$ cat chromium-flags.conf
--password-store=basic
--start-maximized
--disable-sync-preferences
--process-per-sitePS: this is not recommended if someone of you guys stores passwords in chrome, if you do, then better use gnome-keyring , or another way would be not storing passwords at all in your browser and keeping them in KeePass, that way you can randomize the passwords and not reuse the same ones.
Last edited by r0b0t (2019-04-28 10:21:49)
Offline