Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 662088 - gnome-base/gnome-keyring-daemon spawns before /run/user/${user} is mounted by elogind
Summary: gnome-base/gnome-keyring-daemon spawns before /run/user/${user} is mounted by...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2018-07-25 10:21 UTC by Pavel
Modified: 2019-03-21 12:28 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Pavel 2018-07-25 10:21:54 UTC
When PAM gnome-keyring module spawns gnome-keyring-daemon --login, it does so before elogind mounts /var/run/users/${user}.

The gnome-keyring-daemon --login, then opens a socket on the original fs.

After elogind mounts another tmpfs on /var/run/users/${user}, that socket becomes unreachable, and the gnome-keyring-daemon --start instance that will be opened later by the session manager will be unable to retrieve the password from the the first instance opened by PAM

What should we do:

Somehow, we need to ensure that gnome-keyring-daemon waits until elogind mounts the per-user run tmpfs before opening a socket.

Please add this bug to elogind tracker #599470
Comment 1 Mart Raudsepp gentoo-dev 2018-07-25 10:58:47 UTC
I wonder if this is related to bug 652194 too
Comment 2 Pavel 2018-07-25 11:05:17 UTC
(In reply to Mart Raudsepp from comment #1)
> I wonder if this is related to bug 652194 too

Those are moves in the right direction, but they wouldn't do anything with the fact that elogind mounts /run/user/${user} after gnome keyring opens a socket there
Comment 3 Pavel 2018-07-25 12:14:10 UTC
Update, I just found out that removing consolekit somehow makes it so that elogind finishes mounting before gnome-keyring-daemon opens a socket in XDG_RUNTIME_DIR
Comment 4 Sven Eden 2018-07-25 15:45:16 UTC
ConsoleKit2 and elogind can not (really) coexist peacefully. Normally nothing bad happens if you install both but only use one. Starting both could be a problem though.

However, two session trackers are one too many.

Nevertheless I am intrigued, as elogind should

a) not mount something that is already there and
b) mount it before it is needed.

I am also isuing gnome-keyring, and am starting elogind via dbus call, thus without an init script. Everything works so far for me.

Which version of elogind do you have installed?
Comment 5 Pavel 2018-07-26 12:47:39 UTC
Well, removing CK solved my problem with gkr. I should've made a screenshot with two tmpfs mounted. One for CK and one by elogind

Using elogind 235.2-r2