Bug#1039573: cannot authenticate after lock: pam_unix(lightdm:auth): auth could not identify password
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tue, 2023-06-27 at 12:22 +0200, Arturo Borrero Gonzalez wrote:
> I just upgraded lightdm from 1.26.0-8 to 1.32.0-2 and now the greeter wont let me
> login after a session lock (like a laptop suspend or CTRL+ALT+L on xfce4).
>
> This can be found in the logs:
>
> Jun 27 12:08:28 endurance lightdm[91911]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=108) by (uid=0)
> Jun 27 12:08:29 endurance lightdm[92079]: pam_unix(lightdm:auth): auth could not identify password for [arturo]
> Jun 27 12:08:38 endurance lightdm[935]: Session pid=92114: Invalid string length 1869348864 from child
> Jun 27 12:08:38 endurance lightdm[92114]: pam_nologin(lightdm:auth): unexpected response from failed conversation function
> Jun 27 12:08:38 endurance lightdm[92114]: No user selected during authentication
> Jun 27 12:08:38 endurance lightdm[92114]: pam_nologin(lightdm:auth): cannot determine user name
>
> So I suspect there is a bug somewhere in the stack.
Hi Arturo, it does look like there's something fishy from the "Invalid string
length 1869348864" (which looks way too high). Is that reproducible everytime
? Is there something specific/peculiar about your installation? I assume
you're using light-locker as your screen locker?
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSbCukACgkQ3rYcyPpX
RFvWuQf8C0PyAmDiSG3S0kgkVpfUO5amy5Q1Nn23KaSUALZsPyE4AAHvdw24K8RM
C/FvwUNbbYw7PMoAfVeh7/Bc8cwYxitZ7/ZrCaD98eFTmadFijwWyMwi2OvxohJY
cw30ztQhauyfYqp4DkHKMa/6dpRNyHLQjH/7hkqXK9Kg/CTcxJ41DBBepVQpxZTw
Hkrw4+De14tWsh6JCRJ1ml8kNIe02YqCUamuAPUpjr8hMLjeNgdaw/FIaZWsqERk
xxQTT7r8wS2GbWkb6vxSiMAhdGYLck2l1KtktrsDdPnyiCcIxd+Cxph0Dati0q+x
SOZHZMatOJvjAGVOB2+VG+qqzu7ttQ==
=e/LG
-----END PGP SIGNATURE-----
Reply to: