Created attachment 116640 [details] 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
I'm sorry but this is outside of KWin's responsibility.
This is a KDE problem though. If you can kindly refer it to the maintainer that can solve it or the package related to it.
There is no indication that this is a kde problem. All we know is that using two non kde applications don't work in a plasma Wayland session. What we also know is that at least one of those applications is not intended to be used outside of gnome. The problem is certainly not in anything kde provides. If you need user support to set this up please consult the user support of the named applications. Kde's bug tracker is not a user support forum, though. If there is any evidence showing that this is truly a bug in our software, please provide it.
@now-im to help narrow it down, please run "env" in both the X and wayland case and look for differences there wrt gnome keyring.
I filed the sddm issue. I'll look deeper into my env tomorrow. It seems to be a volatile issue for me as its gone from applications not being able to communicate with the gnome-keyring-daemon, to the daemon not starting on login, and back to the daemon starting but not communicating over the last several months. I'll note that I am also on Arch Linux, so there is some possibility of it being a packaging issue as well.
The only differences I see in my env that I'd think *might* have some effect are SHLVL is one higher in Wayland (3) vs X (2) The X session sets GTK_MODULES=canberra-gtk-module, while the Wayland session does not. I don't necessarily think either of these should affect gnome-keyring, but the only other differences are ones I would expect -- thinks like the Wayland session having QT_WAYLAND_DISABLE_WINDOWDECORATION and QT_WAYLAND_FORCE_DPI variables and XDG_VTNR being set to 2 in Wayland instead of 1. No env variables seem to directly relate to gnome-keyring.
I have filed a bug in mailspring as this doesn't seem like a KDE software problem. https://github.com/Foundry376/Mailspring/issues/1257
File it with gnome-keyring.
Filed at https://gitlab.gnome.org/GNOME/gnome-keyring/issues/19