On 02/09/2018 08:05 AM, François Patte wrote: > Le 09/02/2018 à 15:33, Ed Greshko a écrit : >> On 02/09/18 22:13, François Patte wrote: >>> Seems to be an empirical way to solve the problem! Nobody knows what is >>> responsible for such a message (Authenticate result for user cath : >>> User not known to the underlying authentication module)? What is this >>> module and how to inform it that a new user was added? >> >> Well, since I am the only one who has responded to your query and since I only know >> what I have found by using google, I guess nobody knows for sure what is causing the >> problem. > > Trying your trick gives the same result: once the password has been > given, lightdm behaves like if it was a wrong password and user can't log! > >> >> At this point are you more interested in getting that user logged in under lightdm or >> finding out why they have been unable to? > > I am interested in both, it is quite boring that something has been done > somewhere and messages in log files are not enough explicit to solve the > problem.... This tends to make the system more secretive. > > I googled too, and find some answer related to pam, to ldap.... Nothing > about lightdm! Please check the system logs. It may be an issue with libcrypt (e.g. the version desired isn't there). I've had that issue with a laptop before where the PAM system wanted libcrypto.so.6 (which was what was originally installed way back when) but the current version was libcrypto.so.10. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Never test for an error condition you don't know how to handle. - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
