Skip to main content ↑ ↓
Topic: Help with GNOME Keyring Daemon not running (Read 1318 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Help with GNOME Keyring Daemon not running

So VSCode (code package from repo) wants me to sign in to github using the github extension for pulls (otherwise i have to re-sign-in each time manually, which is a pain). But when I sign in and authorize the url, I get this error: https://i.imgur.com/birXKEW.png

I found a command to start gnome keyring (gnome-keyring-daemon --start) but with a specific argument (--components=secrets, so gnome-keyring-daemon --start --components=secrets) as a fix for this issue on an issue tracker (can't find it right now). But running it
 last time I tried gave me the same error along with another one: https://hastebin.com/owarukucol.pl
this time, it gives me no error but the issue isn't fixed, so i'm really damn confused. any ideas? thanks! :D

Re: Help with GNOME Keyring Daemon not running

Reply #1 –
Quote from: codic – on
So VSCode (code package from repo) wants me to sign in to github using the github extension for pulls (otherwise i have to re-sign-in each time manually, which is a pain). But when I sign in and authorize the url, I get this error: https://i.imgur.com/birXKEW.png

I found a command to start gnome keyring (gnome-keyring-daemon --start) but with a specific argument (--components=secrets, so gnome-keyring-daemon --start --components=secrets) as a fix for this issue on an issue tracker (can't find it right now). But running it
 last time I tried gave me the same error along with another one: https://hastebin.com/owarukucol.pl
this time, it gives me no error but the issue isn't fixed, so i'm really damn confused. any ideas? thanks! :D


Please check the  pam status? Gnome Wiki

If the problem persists, please report it at the Announcment of Gnome ISO post, so to improve the testing Gnome ISO.

Re: Help with GNOME Keyring Daemon not running

Reply #2 –
This is the stable *KDE* ISO, not the testing GNOME one. Not the biggest fan of GNOME but some apps need gnome-keyring.
` grep -rq pam_gnome_keyring.so /etc/pam.* && echo "Have PAM Support"` echoes the message, but `test -f ~/.gnome2/keyrings/login.keyring && echo "Have 'login' keyring"` does not...

Re: Help with GNOME Keyring Daemon not running

Reply #3 –
Quote from: codic – on
This is the stable *KDE* ISO, not the testing GNOME one. Not the biggest fan of GNOME but some apps need gnome-keyring.
` grep -rq pam_gnome_keyring.so /etc/pam.* && echo "Have PAM Support"` echoes the message, but `test -f ~/.gnome2/keyrings/login.keyring && echo "Have 'login' keyring"` does not...

Therefore, is an issue of Plasma DE.

Are you on wayland sesion?

Check the issue at Gnome Gitlab, is still open.
 

Re: Help with GNOME Keyring Daemon not running

Reply #4 –
Ah okay, no I'm on x11 so that doesn't apply

Re: Help with GNOME Keyring Daemon not running

Reply #6 –
Code: [Select]
$ sudo mv /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon-old
That might fix it if you are using Chromium - it's a common problem if you have the Gnome keyring daemon installed as a dep for a package that uses the libs, but you are not running Gnome. The daemon doesn't run or do anything, but Chromium finds it in /usr/bin and tries to use it. If you mv the binary then it doesn't and it all works. You might need to repeat it if it gets updated. Also you could find out what requires it and remove the package entirely or swap it for some other similar package without that dep, if it wasn't too inconvenient.