I'm not sure if this is a bug in pam_kwallet (since it has no documentation!) or mageia-kde4-config, but our default /etc/pam.d/kdm file includes two lines with pam_kwallet, one in the auth section and one in the session section. The one in the auth section breaks the PAM stack, making the session section in particular not work. I am using SSSD to authenticate with AD, so pam_mkhomedir needs to be employed to create the home directories. With the auth pam_kwallet line in /etc/pam.d/kdm, it doesn't run pam_mkhomedir (which is the first session line in /etc/pam.d/system-auth) so homedirs don't get created with the correct permissions or with the files from /etc/skel. Removing the auth pam_kwallet line from /etc/pam.d/kdm fixes this. Reproducible: Steps to Reproduce:
CC: (none) => mageiaWhiteboard: (none) => MGA5TOO
IIRC, I used the same pam configuration as Fedora. There are some informations about pam configuration for pam_kwallet in this blog post https://www.dennogumi.org/2014/04/unlocking-kwallet-with-pam
(In reply to Luc Menut from comment #1) > IIRC, I used the same pam configuration as Fedora. confirmed https://fedorahosted.org/kde-settings/browser/trunk/etc/pam.d/kdm and Fedora use exactly the same configuration to open gnome_keyring with pam_gnome_keyring.so .
So our version of pam_kwallet must be broken.
Probably obvious, but uninstalling pam-kwallet also fixes the problem.
*** Bug 17513 has been marked as a duplicate of this bug. ***
CC: (none) => andresalaun
kwallet-pam has replaced pam-kwallet in Cauldron. It builds on Mageia 5, but exhibits the same problem. It's possible that kwallet-pam is also broken, but I'm guessing our /etc/pam.d/kdm config is incorrect. As for Cauldron, kwallet is not included in /etc/pam.d/sddm, so this won't be an issue unless someone tries to enable it modeling the config after Mageia 5's kdm one.
Version: Cauldron => 5Whiteboard: MGA5TOO => (none)
(In reply to David Walser from comment #6) > As for Cauldron, kwallet is not included in /etc/pam.d/sddm, so this won't > be an issue unless someone tries to enable it modeling the config after > Mageia 5's kdm one. How is this handled in an update mga5 -> mga6 ?
CC: (none) => fri
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=18986
Blocks: (none) => 17523
Assignee: lmenut => kde
@ KDE team @ David Walser @ Morgan Are still any issues expected or possible in Mageia 6 that are related to this (Mga5) bug report?
CC: (none) => marja11Keywords: (none) => NEEDINFO
See Comment 6.
Keywords: NEEDINFO => (none)Version: 5 => CauldronWhiteboard: (none) => MGA6TOO
It works with sddm as documented in https://bugs.mageia.org/show_bug.cgi?id=18986#c60 Retested now with current Mga6 Plasma. Ulrich Beckmann *** This bug has been marked as a duplicate of bug 18986 ***
Status: NEW => RESOLVEDCC: (none) => bequimao.deResolution: (none) => DUPLICATE