-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logind-check-graphical=true causes lightdm in LXC container to fail to start #263
Comments
See [this issue on github](canonical/lightdm#263) and [this commit](canonical/lightdm@9c84285)
For #165, |
I'm getting the same behavior on gentoo with openrc and nvidia-drivers since upgrade to LightDM-1.32. With
lightdm is automagically appearing on screens without restarting the service. |
I am not 100% sure but a workaround currently working for me is to wait module |
I tried to force |
Then you can consider try |
I run into the same issue here on RaspberryPi devices both 32bit and 64bit on a 5.15 kernel, even with Additionally... a 20 second pause at startup??? That is not a good workaround at all for a system, and leads to users thinking something is wrong with their devices. |
Hello! I'm running Fedora 36 in an LXC/LXD container with NVIDIA GPU pass through. Today I upgraded LightDM from version 1.30.0 to 1.32.0. I found that Xorg didn't start, but systemctl showed that the LightDM service started successfully.
This is the LightDM log of the failed startup.
This is the LightDM configuration.
This is the raw.lxc configuration.
I compared the config changes of the two versions (
diff lightdm.conf lightdm.conf.rpmnew
):And found that
logind-check-graphical
is set to true by default. After changing to false, Xorg started successfully.I don't know what this option does. It seems to prevent the system from booting so fast that LightDM starts before loading the graphics driver. But in my use case (although it may be rare), I think LightDM is not properly checking the loading status of the graphics driver. Or is my configuration wrong?
The text was updated successfully, but these errors were encountered: