Control: reassign -1 pam-u2f 1.4.0-1 Control: affects -1 sddm Control: affects -1 kde-workspace Control: retitle -1 pam-u2f stops setting $WAYLAND_DISPLAY Hey, > I′m sorry because it′s far beyond my what i′m used to on linux but this is > what i found. Me too. I never dived into the pam system. > You were right, after several tries, i find that it breaks only after making > changes related to YubiKey, but only breaks on Wayland sessions. X11 > sessions still works well. > > The main workaround i identified is to revert pam.d config, to create a new > user. And after not putting back yubikey logging not to break the new user. I reassign to pam-u2f, as it somehow the connection between sddm and pam-u2f. As sddm maintainers are already in the feedback loop ( because sddm is pkg-qt- kde umbrella), I just throw it over the fence to pam-u2f. To get hopefully some information, what may explain why sddm+pam-u2f won't set $WAYLAND_DISPLAY. Maybe you simple need to setup pam-u2f differently with Sddm and Wayland? Regarding the config files - can you please share the diff you did against the default config. So far I see, that you disabled pam_u2f in the configs you share, correct? > Issue is existing users continue to face issues with Wayland sessions after > reverting configuration about yubikey. So i dropped my idea to use yubikey > for logging for now as i prefer to stay on wayland and made a new user. > Just for context, i tried on gnome with GDM and yubikey config didn′t broke > session in x11 and wayland. Okay thanks for this data point. You can also try to use GDM to start a KDE Wayland session? As there is no need to use SDDM ;) Regards, hefee
Attachment:
signature.asc
Description: This is a digitally signed message part.