GNU bug report logs - #47610
gnome-keyring service doesn't appear

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47610 in the body.
You can then email your comments to 47610 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "bdju" <bdju <at> tilde.team>
To: <bug-guix <at> gnu.org>
Subject: gnome-keyring service doesn't appear
Date: Mon, 05 Apr 2021 23:38:19 -0500

guix (GNU Guix) 04ba7a196ab23539f1c7897ca5349fa635c5e88d
I am on Guix System.
Gajim told me I needed a keyring to save my password, so I installed
gnome-keyring in my user's manifest. I then also added its service to my
config.scm and did a reconfigure. After all that, I did a `sudo herd
status` and gnome-keyring was not in the list anywhere.

Message #8 received at 47610 <at> debbugs.gnu.org (full text, mbox):

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: bdju <at> tilde.team
Cc: 47610 <at> debbugs.gnu.org
Subject: bug#47610: gnome-keyring service doesn't appear
Date: Tue, 06 Apr 2021 08:55:42 +0200

gnome-keyring-service is not a shepherd service.  It is a pam service,
that ensures your login keyring (if it exists) is unlocked when you log
in.  That's all it does.

`ps x | grep gnome-keyring` should have a non-empty output.  Mine
includes this:
/gnu/store/47nl5kpkc3sgwasrbk06sgaig22w07ha-gnome-keyring-
3.34.0/bin/gnome-keyring-daemon --daemonize --login

Regards,
Leo

Message #11 received at 47610 <at> debbugs.gnu.org (full text, mbox):

From: "bdju" <bdju <at> tilde.team>
To: "Leo Prikler" <leo.prikler <at> student.tugraz.at>
Cc: 47610 <at> debbugs.gnu.org
Subject: Re: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 21 Apr 2021 01:49:08 -0500

On Tue Apr 6, 2021 at 1:55 AM CDT, Leo Prikler wrote:
> gnome-keyring-service is not a shepherd service. It is a pam service,
> that ensures your login keyring (if it exists) is unlocked when you log
> in. That's all it does.
>
> `ps x | grep gnome-keyring` should have a non-empty output. Mine
> includes this:
> /gnu/store/47nl5kpkc3sgwasrbk06sgaig22w07ha-gnome-keyring-
> 3.34.0/bin/gnome-keyring-daemon --daemonize --login
>
> Regards,
> Leo
The only output I get back from that is the very grep I'm running. I
didn't have gnome-keyring in my manifest, so I added it. Then I
rebooted. Still nothing. I also installed python-keyring.
Someone had me run `keyring --list-backends` which seems to show I have
no working keyring backends. I haven't messed with keyrings before, so
maybe I'm just doing something wrong here.

(output of above command)
```
keyring.backends.fail.Keyring (priority: 0)
keyring.backends.chainer.ChainerBackend (priority: -1)
```

Message #14 received at 47610 <at> debbugs.gnu.org (full text, mbox):

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: bdju <bdju <at> tilde.team>
Cc: 47610 <at> debbugs.gnu.org
Subject: Re: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 21 Apr 2021 09:30:46 +0200

Am Mittwoch, den 21.04.2021, 01:49 -0500 schrieb bdju:
> On Tue Apr 6, 2021 at 1:55 AM CDT, Leo Prikler wrote:
> > gnome-keyring-service is not a shepherd service. It is a pam
> > service,
> > that ensures your login keyring (if it exists) is unlocked when you
> > log
> > in. That's all it does.
> > 
> > `ps x | grep gnome-keyring` should have a non-empty output. Mine
> > includes this:
> > /gnu/store/47nl5kpkc3sgwasrbk06sgaig22w07ha-gnome-keyring-
> > 3.34.0/bin/gnome-keyring-daemon --daemonize --login
> > 
> > Regards,
> > Leo
> The only output I get back from that is the very grep I'm running. I
> didn't have gnome-keyring in my manifest, so I added it. Then I
> rebooted. Still nothing. I also installed python-keyring.
> Someone had me run `keyring --list-backends` which seems to show I
> have
> no working keyring backends. I haven't messed with keyrings before,
> so
> maybe I'm just doing something wrong here.
> 
> (output of above command)
> ```
> keyring.backends.fail.Keyring (priority: 0)
> keyring.backends.chainer.ChainerBackend (priority: -1)
> ```
That's quite an interesting observation.  Could you tell me what DM
(gdm, sddm, sway) you're using?

The gnome-keyring PAM service works by adding an auto_start login
entry, that refers to gnome-keyring's
/lib/security/pam_gnome_keyring.so.  I don't think you need GNOME
keyring installed for that to run, but the default configuration
assumes you're running GDM.  You will need to adjust it if you use
something else.

Regards,
Leo

Message #17 received at 47610 <at> debbugs.gnu.org (full text, mbox):

From: "bdju" <bdju <at> tilde.team>
To: "Leo Prikler" <leo.prikler <at> student.tugraz.at>
Cc: 47610 <at> debbugs.gnu.org
Subject: Re: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 21 Apr 2021 02:35:13 -0500

On Wed Apr 21, 2021 at 2:30 AM CDT, Leo Prikler wrote:
> That's quite an interesting observation. Could you tell me what DM
> (gdm, sddm, sway) you're using?
>
> The gnome-keyring PAM service works by adding an auto_start login
> entry, that refers to gnome-keyring's
> /lib/security/pam_gnome_keyring.so. I don't think you need GNOME
> keyring installed for that to run, but the default configuration
> assumes you're running GDM. You will need to adjust it if you use
> something else.
>
> Regards,
> Leo
I'm using sway, I launch it with `exec sway` from a tty.

Message #20 received at 47610 <at> debbugs.gnu.org (full text, mbox):

From: Leo Prikler <leo.prikler <at> student.tugraz.at>
To: bdju <bdju <at> tilde.team>
Cc: 47610 <at> debbugs.gnu.org
Subject: Re: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 21 Apr 2021 10:05:48 +0200

Am Mittwoch, den 21.04.2021, 02:35 -0500 schrieb bdju:
> On Wed Apr 21, 2021 at 2:30 AM CDT, Leo Prikler wrote:
> > That's quite an interesting observation. Could you tell me what DM
> > (gdm, sddm, sway) you're using?
👆 idiot thinking sway is a DM and not a WM.
> > 
> > The gnome-keyring PAM service works by adding an auto_start login
> > entry, that refers to gnome-keyring's
> > /lib/security/pam_gnome_keyring.so. I don't think you need GNOME
> > keyring installed for that to run, but the default configuration
> > assumes you're running GDM. You will need to adjust it if you use
> > something else.
> > 
> > Regards,
> > Leo
> I'm using sway, I launch it with `exec sway` from a tty.
Since you manually exec sway, you can either configure gnome-keyring-
service, so that it always runs on login (be aware, that I haven't
checked that configuration and it might lock you out forever, so use
rollbacks if that happens), or try to start the keyring manually or
from sway.

Message #25 received at 47610-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Leo Prikler <leo.prikler <at> student.tugraz.at>
Cc: 47610-done <at> debbugs.gnu.org, bdju <bdju <at> tilde.team>
Subject: Re: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 23 Apr 2025 21:15:56 +0900

Hi,

Leo Prikler <leo.prikler <at> student.tugraz.at> writes:

> Am Mittwoch, den 21.04.2021, 02:35 -0500 schrieb bdju:
>> On Wed Apr 21, 2021 at 2:30 AM CDT, Leo Prikler wrote:
>> > That's quite an interesting observation. Could you tell me what DM
>> > (gdm, sddm, sway) you're using?
> 👆 idiot thinking sway is a DM and not a WM.
>> > 
>> > The gnome-keyring PAM service works by adding an auto_start login
>> > entry, that refers to gnome-keyring's
>> > /lib/security/pam_gnome_keyring.so. I don't think you need GNOME
>> > keyring installed for that to run, but the default configuration
>> > assumes you're running GDM. You will need to adjust it if you use
>> > something else.
>> > 
>> > Regards,
>> > Leo
>> I'm using sway, I launch it with `exec sway` from a tty.
> Since you manually exec sway, you can either configure gnome-keyring-
> service, so that it always runs on login (be aware, that I haven't
> checked that configuration and it might lock you out forever, so use
> rollbacks if that happens), or try to start the keyring manually or
> from sway.

gnome-keyring nowadays should be started at boot automatically for GNOME
users, since commit 43c4d16ad9e.  Other environmentbswill need to follow
a manual setup as outlined in (info "(guix) Desktop Services"),
adjusting the pam-services value.

If you could figure it out, perhaps something that would be useful is to
have an example for non-GDM systems added to the manual.  Until then,
I'll close this issue as it should be solvable through configuration.

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.