Summary: | gnome-base/gnome-keyring-3.12 - different gnome-keyring-daemon processes uses the same path for sockets | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Tsoy <alexander> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | gmurray, marduk, poncho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=516848 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Tsoy
2014-07-30 09:00:21 UTC
Do we really need pam_gnome_keyring in /etc/pam.d/system-login? I think it should go into individual pam configs for login managers. $ grep gnome_keyring /etc/pam.d/system-login auth optional pam_gnome_keyring.so password optional pam_gnome_keyring.so session optional pam_gnome_keyring.so auto_start (In reply to Alexander Tsoy from comment #1) > login managers. display managers (In reply to Alexander Tsoy from comment #1) > $ grep gnome_keyring /etc/pam.d/system-login > auth optional pam_gnome_keyring.so > password optional pam_gnome_keyring.so > session optional pam_gnome_keyring.so auto_start I just realized that it is controlled by the gnome-keyring use flag in pambase ebuild. Rebuilding pambase with USE=-gnome-keyring solved this problem for me. (In reply to Alexander Tsoy from comment #0) > Related upstream change: > > [1] > https://git.gnome.org/browse/gnome-keyring/commit/ > ?id=275a696131e41ea4be3d3ddf6690b8bcd0fe0105 So upstream does not support multiple gnome-keyring-daemon instances per user and it's really make no sense to run gnome-keyring-daemon in non-graphical sessions. I think the following blocker should be added to gnome-base/gnome-keyring ebuilds: "!sys-auth/pambase[gnome-keyring]". *** This bug has been marked as a duplicate of bug 516848 *** |