-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi systemd/logind maintainers.
I'm reaching out to you about a bug (#1038611) reported in LightDM which is likely somewhere else in the stack (maybe in logind or maybe in Xorg or the DDX). With the update to 1.32 some people experienced an issue where LightDM wouldn't start. At first it seemed linked to people using NVidia binary driver, but we also had one user on a RaspberryPi 4. Some investigation linked that to a option in lightdm.conf whose default value changed with 1.32. That option is `login-check-graphical` and seems to check if the seat (reported by logind) is marked as graphical or not. Adilson checked and indeed on their installation seat0 is not marked as graphical: > logind-check-graphical=true > loginctl show-seat seat0 > Id=seat0 > CanTTY=yes > CanGraphical=no > Sessions= > IdleHint=yes > IdleSinceHint=0 > IdleSinceHintMonotonic=0 I'm not sure why and I guess it's a bad interaction between logind and the graphical system or something, but I'm not too sure how to investigate more, so I'm adding you to the loop in case you can shine some light. At this point I don't think it's a bug in LightDM but since I'm not sure where the bug is, let's not reassign just yet. Regards, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbEUcACgkQ3rYcyPpX RFuqdwgAkPorc8enxSgGWMBQI+kbX+RX76fQQSxgjN/UHdfkToHFcvZxjUi8uryv J/t6cCUrH9hrs1lcxZDLcoHy5wclbhJ0f2TroUOvtrN5Hstb8dJsr4+uPKGs1Xnz nxfCR3GBl52+6TgPRjqq8/f09L9tOcOmRAjOtpXsnvnAABNZXOx6QWs7gzZ/IVza P4kq+UQBT4ECicySD7cEH0y7zpcEJaLFt7Blf2SrBHo79qMb5lRfheFsJ45lunLs uJ/ATODBMgec9DFAGyzuUbKwbRnkKYSldVlLpgA9KNxzzagUlEDCkfoBXpFE01F2 60yyKJ3I9p0f8duCDKJpY4WneKsMGQ== =Di8i -----END PGP SIGNATURE-----
