Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gnome-keyring-daemon starts in Plasma X session, but not in Wayland #1104

Closed
LoneFenris opened this issue Nov 26, 2018 · 4 comments
Closed

Comments

@LoneFenris
Copy link

I'm not sure if this is an SDDM issue or a Plasma one, but I thought I'd start here.

I have SDDM configured to unlock my gnome-keyring with PAM. This works when launching the normal Plasma session on X, but on the Plasma (Wayland) session, gnome-keyring-daemon doesn't seem to end up getting started. I'll try and pull logs tonight.

@LoneFenris
Copy link
Author

Okay, so the journalctl | grep sddm logs don't seem to show anything different. In fact, gnome-keyring doesn't even show up in them at all, despite it still working in X and not in Wayland. Not sure what other info to provide, though, so:

X session:

sddm[640]: Message received from greeter: Login
sddm[640]: Reading from "/usr/share/xsessions/plasma.desktop"
sddm[640]: Reading from "/usr/share/xsessions/plasma.desktop"
sddm[640]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
sddm-helper[831]: [PAM] Starting...
sddm-helper[831]: [PAM] Authenticating...
sddm-helper[831]: [PAM] Preparing to converse...
sddm-helper[831]: [PAM] Conversation with 1 messages
sddm-helper[831]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
sddm-helper[831]: [PAM] returning.
sddm[640]: Authenticated successfully
sddm-greeter[740]: Message received from daemon: LoginSucceeded
sddm-helper[831]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
sddm-helper[831]: pam_unix(sddm:session): session opened for user lonefenris by (uid=0)
sddm-helper[730]: pam_unix(sddm-greeter:session): session closed for user sddm
sddm-helper[831]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
sddm-helper[847]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
sddm-helper[730]: [PAM] Closing session
sddm-helper[730]: [PAM] Ended.
sddm[640]: Auth: sddm-helper exited successfully
sddm[640]: Greeter stopped.
sddm-helper[831]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startkde\""
sddm-helper[849]: Adding cookie to "/home/lonefenris/.Xauthority"
sddm[640]: Session started

Wayland session:

sddm[607]: Message received from greeter: Login
sddm[607]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
sddm[607]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
sddm[607]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "dbus-run-session /usr/bin/startplasmacompositor"
sddm-helper[765]: [PAM] Starting...
sddm-helper[765]: [PAM] Authenticating...
sddm-helper[765]: [PAM] Preparing to converse...
sddm-helper[765]: [PAM] Conversation with 1 messages
sddm-helper[765]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
sddm-helper[765]: [PAM] returning.
sddm[607]: Authenticated successfully
sddm[607]: Jumping to VT 2
sddm[607]: VT mode didn't need to be fixed
sddm-helper[765]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
sddm-helper[765]: pam_unix(sddm:session): session opened for user lonefenris by (uid=0)
sddm-helper[765]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
sddm-helper[785]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
sddm-helper[765]: Starting: "/usr/share/sddm/scripts/wayland-session dbus-run-session /usr/bin/startplasmacompositor"
sddm[607]: Session started

@LoneFenris
Copy link
Author

I'm now thinking this may be a bug in Plasma instead. After the 5.14.4 update, the gnome-keyring-daemon is started under the Wayland session, now, but can't be communicated with by the applications

journalctl | grep gnome-keyring:

gnome-keyring-daemon[819]: **
audit[819]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=819 comm="gnome-keyring-d" exe="/usr/bin/gnome-keyring-daemon" sig=6 res=1
kernel: audit: type=1701 audit(1543591980.271:50): auid=1000 uid=1000 gid=1000 ses=2 pid=819 comm="gnome-keyring-d" exe="/usr/bin/gnome-keyring-daemon" sig=6 res=1
gnome-keyring-daemon[1502]: couldn't connect to control socket at: /run/user/1000/keyring/control: Connection refused
gnome-keyring-d[1502]: couldn't connect to control socket at: /run/user/1000/keyring/control: Connection refused

@davidedmundson
Copy link
Member

SDDM handles PAM the same for X and wayland.
It's not an SDDM issue.

@Mazino-Urek
Copy link
Contributor

@LoneFenris Hey, I have just filed a bug in KDE forum but they are not convinced that this is a KDE problem either. Can you kindly provide your inside their as I lack technical knowledge? The link is below:
https://bugs.kde.org/show_bug.cgi?id=401681

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants