https://bugs.kde.org/show_bug.cgi?id=401681
Bug ID: 401681
Summary: libsecrect/ gnome-keyring not working under wayland
Product: kwin
Version: 5.14.4
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: now.im....@gmail.com
Target Milestone: ---
Created attachment 116640
--> https://bugs.kde.org/attachment.cgi?id=116640&action=edit
Mailspring error message
SUMMARY
I am not sure this is a Kwin specific bug. I use mailspring that needs
libsecrect and gnome-keyring. It does not use kwallet as it does not support
libsecret. I have edited the /etc/pam.d/login file according to archwiki in
order to unlock gnome-keyring at login.
https://wiki.archlinux.org/index.php/GNOME/Keyring#Using_the_keyring_outside_GNOME
Under x session, it works fine but under wayland mailspring shows an error
message that I have included in the attachment. A similar bug has been posted
in sddm github page.
https://github.com/sddm/sddm/issues/1104
STEPS TO REPRODUCE
1. Opening an app that uses gnome-keyring under wayland
OBSERVED RESULT
gnome-keyring not unlocked when starting the system.
EXPECTED RESULT
Seamless libsecret/ gnome-keyring integration when pam file is edited.
SOFTWARE/OS VERSIONS
Windows: n/a
MacOS: n/a
Linux/KDE Plasma: Linux 4.19
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.52.0
Qt Version: 5.11
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
