unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: bdju <bdju@tilde.team>
Cc: 47610@debbugs.gnu.org
Subject: bug#47610: gnome-keyring service doesn't appear
Date: Wed, 21 Apr 2021 10:05:48 +0200	[thread overview]
Message-ID: <87795d2fba7cae6274463d9a013cd494a020eaef.camel@student.tugraz.at> (raw)
In-Reply-To: <CAT88MFAVDG7.WJ3TR1RJ3PDW@masaki>

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.





      reply	other threads:[~2021-04-21  8:10 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
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 [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87795d2fba7cae6274463d9a013cd494a020eaef.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=47610@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).