Solus Budgie Unlock keyring pop-up
[deleted]
- Edited
Vivaldi stores some data (saved passwords, iirc) on the keyring and the automatic login unfortunately doesn't unlock the keyring automatically. The behavior is the same with gnome-keyring and kwallet. There are workarounds for that, such as setting an empty password as the keyring password, but you're on your own to evaluate the potential security implications on that.
In my point of view, you weren't rude.
- Edited
[deleted] Vivaldi stores some data (saved passwords, iirc) on the keyring and the automatic login unfortunately doesn't unlock the keyring automatically. The behavior is the same with gnome-keyring and kwallet. There are workarounds for that, such as setting an empty password as the keyring password, but you're on your own to evaluate the potential security implications on that.
Yep, thanks this is a bit like what @Sebastian wrote too, well, hmm... it's just the way things are then. I find it very strange though. I mean auto-login really appears to be "useless exercise" then. I'm sure I'm not the last person who will ponder this when it "works" like this.
It's Linux--you got to roll with it.
I would just
A) rip all passwords out of vivaldi (disable it) and cut and paste from a password manager so you never have use that stupid keyring again.
then B) uninstall/reinstall vivaldi
or
C) use another browser purely for login accounts.
or
I wonder if you monkey with anything in /.config/vivaldi vivaldi settings?
or
type 'disable vivaldi keyring prompt' into DDG and see if there's an easy fix
or
see if it persists if you make solus autostart it
that is the end of my brain
- Edited
brent It's Linux--you got to roll with it
Hah! How uplifting post!
One thing... I DON'T have any passwords stored in vivaldi. I never store any passwords in my browser.
Other points you made... I must think about them for awhile
Another thing comes to mind: This is quite recent install of Solus and I remember enabling auto-login (during install), which later I found out that, that setting didn't stick. So I enabled it again via Budgie Control Centre!
I have not messed with ./config/vivaldi settings. Vivaldi has been updated like everything else in this quite recent install.
DDG=duckduckgo, right?
Could it be as easy and a clean cache/history?
or uninstall/reinstall plus throw away to trash every folder connected to vivaldi in /home, after uninstall..
you lose your bookmarks but maybe no keyring
[deleted]
brent No. Vivaldi and other Chromium browsers want keyring access regardless of whether there are any saved passwords.
[deleted] interesting. the only chrome derivative I run is ungoogledand it never activates keyring access. (Eloston probably baked that out of ungoogled).
But all the times I used Vivaldi I never got a keyring login prompt either. Or all the times I used Brave.
Wonder why some get afflicted with this and some don't?
Now I wonder if there is a tie-in to the autologin at boot?
[deleted]
brent You probably don't have the automatic session login enabled. When you log in by entering your password, the keyring gets unlocked right away.
- Edited
[deleted] ok thanks. easy solution then (don't autolog) @wetgeek was right).
qk4-li3 I can't imagine this problem persisting, someone will fix it upstream somewhere, someday. seems. I am going to search engine this for kicks
edit: info from 2019 but seems quite a few ways to disable: https://askubuntu.com/questions/31786/chrome-asks-for-password-to-unlock-keyring-on-startup#968149
Reminds me got fix my brave from doing that on this install its a backup browser now.
- Best Answerset by qk4-li3
Chromium applications like Vivaldi will create an entry in the libsecret backend (gnome-keyring on Budgie) often regardless of whether or not you actually do anything that requires it. gnome-keyring requires a password to unlock the vault, this defaults to the password that you set when you installed the system. When you do not have auto-login enabled the greeter (lightdm for Budgie by default) captures your password when you login to the session and feeds that to gnome-keyring in order to automatically unlock it. When you have auto-login enabled this auto-unlock never happens which is why gnome-keyring needs to be unlocked manually when it's invoked for the first time in a session.
This is all expected behavior, though it is often surprising to people using auto-login who are not familiar with it. You pretty much have only a few options here:
- Ignore it and just accept that you'll need to enter your password whenever you start something that uses libsecret to store encryption keys or credentials.
- Disable auto-login so that your password is captured when you login via the greeter and gnome-keyring is unlocked with that password.
- Change the gnome-keyring password to an empty string. Note that this will remove encryption from all secrets protected by gnome-keyring and all secrets will be readable by any application that has read access to your home directory. This is insecure and I would not recommend this.
ReillyBrogan Is plasma different in that respect then?
Axios It uses kwallet instead of gnome-keyring as the libsecret backend, but the behavior is basically the same here.
I do #3 but dont use any linux machines for accessing online accounts except this forum and right now thats from
firefox instead of brave.
At some point will migrate that from mac prob and this is important info to know.
Thanx
Axios
I really didn't get this entirely until he explained it.
manual login=you are logged into the OS; no other credential asked for again; keyring satisfied at the DM stage
autologin=because of browser tentacles you must furnish your credentials to the OS at the request of the browser...
read that bold part again. goofy ain't it? but all part of the keyring apparatus from the beginning and it is always "expected" no doubt..
#3 might suit you if you only use solus acct but anything else.
" 3. Change the gnome-keyring password to an empty string. Note that this will remove encryption from all secrets protected by gnome-keyring and all secrets will be readable by any application that has read access to your home directory. This is insecure and I would not recommend this.
on the other hand the amount of applications that have access to /home is pretty big methinks.