[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, 2023-08-08 at 01:25 -0500, Steev Klimaszewski wrote:
> I'm running into a very similar issue as the original submitter,
> however, when I'm running into it, I am *not* using the nVidia binary
> driver, but I am using a custom 5.15.44 kernel for a Raspberry Pi.
> What I found after digging for quite a while, was that, yes,
> downgrading to 1.26 would start Xorg, and upgrading to 1.32 would
> cause it to not start Xorg.  After diffing the contents between 1.26
> and 1.32, it seems that the option "logind-check-graphical" has
> changed from the default of false, to a default of true.
> 
> Simply adding in
> 
> logind-check-graphical=false
> 
> under the [LightDM] heading in /etc/lightdm/lightdm.conf shows it as
> starting again.  This happened for me on both Pi3 and Pi4, armhf and
> arm64.  I'm not entirely sure why this is the case, and the kernel
> hasn't changed on these devices since 2022-07-03 when we last built
> the kernel for them.  Perhaps the original submitter could also see if
> changing that option works for them with the nVidia binary driver?

Hi Steev and Adilson,

so it might be linked to https://github.com/canonical/lightdm/issues/263

Looking at a bug linked from above
(https://github.com/canonical/lightdm/issues/165) it looks like the default
was changed in order to fix a race condition or something.

The documentation says:

# logind-check-graphical = True to on start seats that are marked as graphical
by logind

Could you check the lightdm.log and check if you have messages about seats
beeing added and whether it's graphical or not (you can add logs here). With
both value for the logind-check-graphical option.

It looks to me that there's an issue deeper in the stacks (in the NVIDIA stuff
or in the RPi graphical stuff) and maybe the seats arent't marked as graphical
or something. So it's ok to tune the option locally as a workaround, but I'm
not sure about reverting it globally.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUZgJIACgkQ3rYcyPpX
RFtkzAgAvSJE1yDFRCZrdI/1zGTW/SWH2KUXuxpYw8b+LrwcvkLBVwSzQhkxKkS4
rd8VUjRRXVcaPXTrPJxeKqObAAYN2iUhiFCKdYAYUxdvlIPWxOkQEf8CeLm/AG6f
rCaHMmQNZY5SFkTCQ5AGUzH38IAp3a4Sdn3E+x1xVMsiYGn6h5I/z0eDcx5135mP
omuBRUYZGnoTfsApetBOQCK7pMzUJX1QRxdaiMjLZCUEsKjwoJc/6ZaLSHB4goYQ
AXAYcrc4jOhYfv6KFqbaxEBWxR/gbdG8+YBh2u8a44KEniJgXl+T4FEKfTA1poxc
muyLJuBzqpHqGyfOvZS73TjWPVZcHw==
=Lrpk
-----END PGP SIGNATURE-----


Reply to: