all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "bdju" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Leo Prikler" <leo.prikler@student.tugraz.at>
Cc: 47610@debbugs.gnu.org
Subject: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 21 Apr 2021 01:49:08 -0500	[thread overview]
Message-ID: <CAT79BYR3Q6R.1QNKNMJHN7X87@masaki> (raw)
In-Reply-To: <f818337bb25d8402279bc93ca8b4a4947f97195c.camel@student.tugraz.at>

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)
```





  reply	other threads:[~2021-04-21  6:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06  4:38 bug#47610: gnome-keyring service doesn't appear bdju via Bug reports for GNU Guix
2021-04-06  6:55 ` Leo Prikler
2021-04-21  6:49   ` bdju via Bug reports for GNU Guix [this message]
2021-04-21  7:30     ` Leo Prikler
2021-04-21  7:35       ` bdju via Bug reports for GNU Guix
2021-04-21  8:05         ` Leo Prikler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAT79BYR3Q6R.1QNKNMJHN7X87@masaki \
    --to=bug-guix@gnu.org \
    --cc=47610@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    --cc=leo.prikler@student.tugraz.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.