FS#60867 - [gnome-keyring] issue on Plasma Wayland session in sddm
Attached to Project:
Arch Linux
Opened by Kyle Tirak (hamsterkill) - Monday, 19 November 2018, 22:01 GMT
Last edited by Toolybird (Toolybird) - Sunday, 25 June 2023, 20:50 GMT
Opened by Kyle Tirak (hamsterkill) - Monday, 19 November 2018, 22:01 GMT
Last edited by Toolybird (Toolybird) - Sunday, 25 June 2023, 20:50 GMT
|
Details
Description:
I'm honestly not sure where this bug is coming from since there's several packages that seem to be involved and I don't have another system to test with a different distribution to even know if it's an upstream issue. I'm happy to report this upstream if it is such an issue, I'd just need to know which upstream project is the likely culprit in this case. When logging in via SDDM into the Plasma Wayland session, gnome-keyring does not seem to work as it is supposed to. Logging in to the standard Plasma session with X still works and automatically unlocks gnome-keyring as expected. Example error from seahorse: (seahorse:4926): seahorse-WARNING **: 21:44:20.319: gkr-backend.vala:94: couldn't connect to secret service: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached gnome-keyring-daemon is running, however. Additional info: gnome-keyring 1:3.28.2-1 sddm 0.18.0-1 plasma-desktop 5.14.3-1 plasma-wayland 5.14.3-1 wayland 1.16.0-1 Steps to reproduce: Launch SDDM Choose Plasma Wayland session Login Try to use an application with secrets stored in gnome-keyring |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 25 June 2023, 20:50 GMT
Reason for closing: Fixed
Additional comments about closing: @MarsSeed "As per testing report by Bernie Innocenti (codewiz) (14 April 2021), problem is resolved. As per original poster's followup comments, this was an issue in gnome-keyring but has been fixed there."
Sunday, 25 June 2023, 20:50 GMT
Reason for closing: Fixed
Additional comments about closing: @MarsSeed "As per testing report by Bernie Innocenti (codewiz) (14 April 2021), problem is resolved. As per original poster's followup comments, this was an issue in gnome-keyring but has been fixed there."
/etc/pam.d/sddm:
#%PAM-1.0
auth include system-login
-auth optional pam_gnome_keyring.so
-auth optional pam_kwallet5.so
account include system-login
password include system-login
-password optional pam_gnome_keyring.so use_authtok
session optional pam_keyinit.so force revoke
session include system-login
-session optional pam_gnome_keyring.so auto_start
-session optional pam_kwallet5.so auto_start
ps aux | grep keyring (under X):
hamster+ 8307 0.1 0.0 316440 6652 ? Sl 11:43 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
hamster+ 8954 0.0 0.0 242332 7264 ? Sl 11:43 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
Under Plasma Wayland, the second entry (with "--start --foreground --components=secrets") is missing. Attempting to run that command after session start does not appear to resolve the issue, either. Only running the command with "--replace" seems to work (and thus requires inputting the keyring password manually as well).
Upstream issue: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/19
Possible fix: https://gitlab.gnome.org/GNOME/gnome-keyring/merge_requests/19
Seahorse works normally.