https://bugs.kde.org/show_bug.cgi?id=400929
--- Comment #4 from PhobosK <phob...@fastmail.fm> --- The same issue still persists. Actually I have never been able to use pam-kwallet properly. The system is still Gentoo, though some of the versions are a lot more recent: lightdm 1.30.0 kwallet-pam - 5.17.2 pam - 1.3.1 plasma-workspace - 5.17.2 plasma-framework - 5.63.0 PAM files are the same as in my previous post. The errors are like as in @Dmitry's logs... I added some extra debug code in the pam_kwallet.c to get some extra info: lightdm[940510]: pam_kwallet5(lightdm:auth): (null): pam_sm_authenticate lightdm[940510]: pam_kwallet5(lightdm:setcred): pam_kwallet5: pam_sm_setcred lightdm[940510]: pam_kwallet5(lightdm:session): pam_kwallet5: pam_sm_open_session lightdm[940567]: pam_kwallet5: final socket path: /run/user/501/kwallet5.socket lightdm[940567]: pam_kwallet5-kwalletd: Couldn't listen in socket because: 95-Operation not supported lightdm[940510]: pam_kwallet5(lightdm:session): pam_kwallet5: Couldn't fork to execv kwalletd (default state of the switch) because of status: 256-1 I am not an expert in sockets coding and operations, but it seems there is a problem with the socket usage at listen(envSocket, 5) level - with this error 95. Besides the forked child at start_kwallet(...) obviously exits with error because of this(256 is the status value and the 1 is the WEXITSTATUS(status)) The folder /run/user/501 has the appropriate user permissions Anyone of the developers? Do you need more debug info? This is already a year old problem that has not been still resolved :( -- You are receiving this mail because: You are watching all bug changes.
