Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Hi Yves, > Em seg., 2 de out. de 2023 às 09:25, Yves-Alexis Perez > escreveu: >> >> On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote: >> > Hi. >> > >> > Here are the logs with and without the "logind-check-graphical=false" >> > option. >> > >> > With this opinion, a new seat is added and no seat is added when this >> > option is commented. >> >> Thanks for the log. I'm unsure if there's no seat at all or if the seat >> is marked as "non graphical" in logind. >> >> In both cases and before logging in as an user, so when lightdm is >> started and a greeter is displayed (with =false) or you get the black >> screen (with =true), could you check the loginctl output (as root)? >> >> I'm not too sure where to look, but at least: >> >> - loginctl >> - loginctl list-seats >> - loginctl show-seat seat0 >> >> Regards, >> -- >> Yves-Alexis Unfortunately, I don't have access to a Raspberry Pi at the moment to do this testing (a user was giving me remote access while they sat at it), but I do have one on the way. We (Kali) have no issue with changing the configuration option locally on our Raspberry Pi images, but it would be nice to track down why this is. From what I've heard, debian testing images do not show the same issue, so it very well could be a fix in a newer kernel than what we have available to use (we can't upgrade due to the wifi firmware we need to use with our images), but I also plan to look into if the same occurs with the Pi5 when it shows up. --steev
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Em seg., 2 de out. de 2023 às 16:30, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, 2023-10-02 at 16:09 -0300, Adilson dos Santos Dantas wrote: > > Ok. Running the command "loginctl show-seat seat0" with lightdm 1.26.0-8 > and > > this option above: > > Id=seat0 > > CanTTY=yes > > CanGraphical=no > > Sessions= > > IdleHint=yes > > IdleSinceHint=0 > > IdleSinceHintMonotonic=0 > > And does LightDM starts correctly with the greeter? > No. LightDM does not start Xorg. - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbGlIACgkQ3rYcyPpX > RFsO8QgAtbR7v03OgNuubCD1/IK8s/quSCltCg9ctR2vWLwK8sPIUkQjx6PFv7mV > nrrS/OpCU5O2ihj/7qdARhHEulLDsYwg6eosOvRccjoxYtwSdSkNR5pBU9WqWQKR > 2kZqunQfcsOlMPcDbULy1QMR636f2U+oA836tUulvjBj1KS9nVoIL1yBjHdC78jY > ln1xv4x3nx+/KWbISeHfSVfNnxAXhnEH7jKyoLJ6MR6xwgon48GGpLuFqhgQpz4T > UbZ12PA0t9zC/YJn2MxFP7Z3HJlXTW5NNhzrBbDmT6F2vciWNdghePq1FGY7yMWV > xz7Us8AyE3flcZWNmHCesqr4L36O8w== > =U+h1 > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2023-10-02 at 16:09 -0300, Adilson dos Santos Dantas wrote: > Ok. Running the command "loginctl show-seat seat0" with lightdm 1.26.0-8 and > this option above: > Id=seat0 > CanTTY=yes > CanGraphical=no > Sessions= > IdleHint=yes > IdleSinceHint=0 > IdleSinceHintMonotonic=0 And does LightDM starts correctly with the greeter? - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbGlIACgkQ3rYcyPpX RFsO8QgAtbR7v03OgNuubCD1/IK8s/quSCltCg9ctR2vWLwK8sPIUkQjx6PFv7mV nrrS/OpCU5O2ihj/7qdARhHEulLDsYwg6eosOvRccjoxYtwSdSkNR5pBU9WqWQKR 2kZqunQfcsOlMPcDbULy1QMR636f2U+oA836tUulvjBj1KS9nVoIL1yBjHdC78jY ln1xv4x3nx+/KWbISeHfSVfNnxAXhnEH7jKyoLJ6MR6xwgon48GGpLuFqhgQpz4T UbZ12PA0t9zC/YJn2MxFP7Z3HJlXTW5NNhzrBbDmT6F2vciWNdghePq1FGY7yMWV xz7Us8AyE3flcZWNmHCesqr4L36O8w== =U+h1 -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Em seg., 2 de out. de 2023 às 15:48, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, 2023-10-02 at 15:33 +0200, Yves-Alexis Perez wrote: > > At that point I don't think it's a problem in LightDM and I don't really > > think it's a good idea to generalize the workaround (and divert from > > upstream). > > Just to be sure, can you test with: > - - LightDM 1.26 - - login-check-graphical=true > Ok. Running the command "loginctl show-seat seat0" with lightdm 1.26.0-8 and this option above: Id=seat0 CanTTY=yes CanGraphical=no Sessions= IdleHint=yes IdleSinceHint=0 IdleSinceHintMonotonic=0 > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbEHAACgkQ3rYcyPpX > RFv38AgA5qxC4JCT1rzmu8ibemyV21C+VQIY+W+TIXw/IOBnWOmZskFeBY7VXdvY > 4+simhXUdijgULROQKSHmhefO+AXSBbLXU8CPM0n89O3FIr1Fjyraff/bj+NEZUZ > FoNeSBdYI8jQ0PK5BE9zXEWgseMrCDXy3w9YmoZcliIB/gvjr2cdoeKo/9V7+1lA > jTvILl5MoaHRywdLVi7F3VAKGrhVJzUJU+CzNFFG7gFEhfQIWb9vlZ9gfO+Os7bC > +jsK91J5+hg8tPWBUGnVNNv8JjQusMUy2XBw6m0SzuUl8UhuaCZ+wmYYklryd0Hq > h7YKEzgKNsM3Bo3kQMIqS8snTCt6/w== > =MFQU > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2023-10-02 at 15:33 +0200, Yves-Alexis Perez wrote: > At that point I don't think it's a problem in LightDM and I don't really > think it's a good idea to generalize the workaround (and divert from > upstream). Just to be sure, can you test with: - - LightDM 1.26 - - login-check-graphical=true Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbEHAACgkQ3rYcyPpX RFv38AgA5qxC4JCT1rzmu8ibemyV21C+VQIY+W+TIXw/IOBnWOmZskFeBY7VXdvY 4+simhXUdijgULROQKSHmhefO+AXSBbLXU8CPM0n89O3FIr1Fjyraff/bj+NEZUZ FoNeSBdYI8jQ0PK5BE9zXEWgseMrCDXy3w9YmoZcliIB/gvjr2cdoeKo/9V7+1lA jTvILl5MoaHRywdLVi7F3VAKGrhVJzUJU+CzNFFG7gFEhfQIWb9vlZ9gfO+Os7bC +jsK91J5+hg8tPWBUGnVNNv8JjQusMUy2XBw6m0SzuUl8UhuaCZ+wmYYklryd0Hq h7YKEzgKNsM3Bo3kQMIqS8snTCt6/w== =MFQU -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
On Mon, Oct 02, 2023 at 09:47:38AM -0300, Adilson dos Santos Dantas wrote: > Here are the results of 'loginctl show-seat seat0' from both > 'login-check-grafical' options. > > logind-check-graphical=true > loginctl show-seat seat0 > Id=seat0 > CanTTY=yes > CanGraphical=no > Sessions= > IdleHint=yes > IdleSinceHint=0 > IdleSinceHintMonotonic=0 > > logind-check-graphical=false > loginctl show-seat seat0 > Id=seat0 > ActiveSession=c1 > CanTTY=yes > CanGraphical=no > Sessions=c1 > IdleHint=no > IdleSinceHint=0 > IdleSinceHintMonotonic=0 > Thanks, so that confirm the issue on your installation: the seat is marked as non graphical for some reason (likely related to the graphics drivers but honestly I'm not too sure). At that point I don't think it's a problem in LightDM and I don't really think it's a good idea to generalize the workaround (and divert from upstream). I'll ping the logind/systemd people with a summary, in case they have an idea here. Regards, -- Yves-Alexis Perez
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Here are the results of 'loginctl show-seat seat0' from both 'login-check-grafical' options. logind-check-graphical=true loginctl show-seat seat0 Id=seat0 CanTTY=yes CanGraphical=no Sessions= IdleHint=yes IdleSinceHint=0 IdleSinceHintMonotonic=0 logind-check-graphical=false loginctl show-seat seat0 Id=seat0 ActiveSession=c1 CanTTY=yes CanGraphical=no Sessions=c1 IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 Best regards, Adilson Em seg., 2 de out. de 2023 às 09:25, Yves-Alexis Perez escreveu: > On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote: > > Hi. > > > > Here are the logs with and without the "logind-check-graphical=false" > > option. > > > > With this opinion, a new seat is added and no seat is added when this > > option is commented. > > Thanks for the log. I'm unsure if there's no seat at all or if the seat > is marked as "non graphical" in logind. > > In both cases and before logging in as an user, so when lightdm is > started and a greeter is displayed (with =false) or you get the black > screen (with =true), could you check the loginctl output (as root)? > > I'm not too sure where to look, but at least: > > - loginctl > - loginctl list-seats > - loginctl show-seat seat0 > > Regards, > -- > Yves-Alexis > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote: > Hi. > > Here are the logs with and without the "logind-check-graphical=false" > option. > > With this opinion, a new seat is added and no seat is added when this > option is commented. Thanks for the log. I'm unsure if there's no seat at all or if the seat is marked as "non graphical" in logind. In both cases and before logging in as an user, so when lightdm is started and a greeter is displayed (with =false) or you get the black screen (with =true), could you check the loginctl output (as root)? I'm not too sure where to look, but at least: - loginctl - loginctl list-seats - loginctl show-seat seat0 Regards, -- Yves-Alexis
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Hi. Here are the logs with and without the "logind-check-graphical=false" option. With this opinion, a new seat is added and no seat is added when this option is commented. Regards, Adilson Em dom., 1 de out. de 2023 às 11:22, Yves-Alexis Perez escreveu: > -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- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=1740 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) [+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ [+0.01s] DEBUG: Monitoring logind for seats [+0.01s] DEBUG: New seat added from logind: seat0 [+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no [+0.01s] DEBUG: Seat seat0: Starting [+0.01s] DEBUG: Seat seat0: Creating greeter session [+0.01s] DEBUG: Seat seat0: Creating display server of type x [+0.01s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than the configured minimum of 7 so not replacing it [+0.01s] DEBUG: Quitting Plymouth [+0.03s] DEBUG: Using VT 7 [+0.04s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.04s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.04s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.04s] DEBUG: XServer 0: Launching X Server [+0.04s] DEBUG: Launching process 1849: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nol
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-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
I tested this solution from Steev Klimaszewski and it worked. So we have a workaround for this problem. Maybe it can be used with sddm. But I need to see where the configuration is to do that. Best regards, Adilson -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Hi Yves, 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?
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Yes, I was able to upgrade lightdm to 1.32 after I reinstalled xserver-xorg. I don't think it was lightdm causing the issue itself, it was due to xserver-xorg and xinit being removed during the a system upgrade. Once I had those re-installed everything is working great again. Thanks for the follow-up. Sent with Proton Mail secure email. --- Original Message --- On Wednesday, June 21st, 2023 at 12:46 AM, Yves-Alexis Perez wrote: > On Wed, 2023-06-21 at 01:59 +, solneman33 wrote: > > > I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and > > reinstalled xserver-xorg and xinit. That resolved the issue for me on both > > machines. > > > > I've never reported a bug before, my apologies if this is incorrect > > procedure. > > > Well, can you check by reinstalling lightdm 1.32 but making sure you have > xserver-xorg? > > Regards, > -- > Yves-Alexis
Processed: Re: Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Processing control commands: > severity -1 important Bug #1038611 [lightdm] lightdm: Lightdm fails to start X after upgrade to 1.32.0 Severity set to 'important' from 'grave' > retitle -1 lightdm 1.32 fails to start X on nvidia binary driver Bug #1038611 [lightdm] lightdm: Lightdm fails to start X after upgrade to 1.32.0 Changed Bug title to 'lightdm 1.32 fails to start X on nvidia binary driver' from 'lightdm: Lightdm fails to start X after upgrade to 1.32.0'. -- 1038611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
control: severity -1 important control: retitle -1 lightdm 1.32 fails to start X on nvidia binary driver On Thu, Jun 22, 2023 at 01:10:41AM -0300, Adilson dos Santos Dantas wrote: > I tested with the nouveau driver and it worked. > > Maybe there is something between 1.26 and 1.32 that conflicts with nvidia > driver. Yes it's likely. > > And it is also similar to #996503 which affects sddm and it worked too with > nouveau. Ack. As I understand it, X doesn't even start at all so it's likely unrelated to LightDM or sddm actually. Could you try in a terminal to just start X (with the `X` command), with NVidia and with Nouveau drivers, and report back? > > I tried to fix this by removing some module options from > https://forums.developer.nvidia.com/t/display-manager-sddm-lightdm-not-starting-with-nvidia-driver/243992 > but it had no effect. > > Maybe forwarding this to nvidia-driver should get some hints about this Yes, feel free to do it and report back any progress. I'm lowering the bug severity as well so it does migrate. Regards, -- Yves-Alexis Perez
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
I tested with the nouveau driver and it worked. Maybe there is something between 1.26 and 1.32 that conflicts with nvidia driver. And it is also similar to #996503 which affects sddm and it worked too with nouveau. I tried to fix this by removing some module options from https://forums.developer.nvidia.com/t/display-manager-sddm-lightdm-not-starting-with-nvidia-driver/243992 but it had no effect. Maybe forwarding this to nvidia-driver should get some hints about this issue. Regards, Adilson Em qua., 21 de jun. de 2023 às 15:23, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote: > > These messages are when I stop lightdm. > > Ah ok. > > > > > > > > > Also is there something peculiar about your hardware (Nvidia/AMD GPU > for > > > example?) or software (specific configuration or something). > > > > > > I'm using Nvidia GPU: > > > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX > > 1650] (rev a1) > > > > And it is using its official drivers: > > > > dpkg -l xserver-xorg > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > > pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Nome Versão Arquitectura Descrição > > +++-==--- > > = > > ii xserver-xorg 1:7.7+23 amd64X.Org X server > > > > dpkg -l xserver-xorg-video-nvidia > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > > pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Nome Versão Arquitectura Descrição > > +++-=--- > > = > > ii xserver-xorg-video-nvidia 530.41.03-1 amd64NVIDIA binary > Xorg > > driver > > Yup, that's likely related. Honestly we (I) don't really support > binary/proprietary drivers. It'd help if you could test with free drivers > (nouveau or something maybe). > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSTQAAACgkQ3rYcyPpX > RFu7Ggf9FCsjsiXteQ+xDSolGEtK2a9eBlnCnI9MY3wY2OdOHJlNCpbEjamWVbw3 > CwEn4//IWPgFmLcKBD1A9ySYein2tY3CDdNH5fii7ZZ/MNAlL1vuKAVuV30ayQtU > V/4xxQXgJ+1JUCPzzKNGMdLs/yumAiLGAs3XzhjUmjVPQWMRWanCOf8dFavDyFG3 > 4sPS6niMeFUWqM17K0ja7VPVj2QbQQSe34jec93W+zcbnxbWZZuJY9nQ2PsQjRDd > /FY0fBQtzopnZMBgRUdYNj09QGuI8kn6dZdD93+/MS2uP95ES7v1nG0bKARrGor7 > pNaWlBMeMGI/+bL89SFEQdR52n/uFw== > =tTX8 > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote: > These messages are when I stop lightdm. Ah ok. > > > > > > Also is there something peculiar about your hardware (Nvidia/AMD GPU for > > example?) or software (specific configuration or something). > > > I'm using Nvidia GPU: > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX > 1650] (rev a1) > > And it is using its official drivers: > > dpkg -l xserver-xorg > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nome Versão Arquitectura Descrição > +++-==--- > = > ii xserver-xorg 1:7.7+23 amd64 X.Org X server > > dpkg -l xserver-xorg-video-nvidia > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nome Versão Arquitectura Descrição > +++-=--- > = > ii xserver-xorg-video-nvidia 530.41.03-1 amd64 NVIDIA binary Xorg > driver Yup, that's likely related. Honestly we (I) don't really support binary/proprietary drivers. It'd help if you could test with free drivers (nouveau or something maybe). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSTQAAACgkQ3rYcyPpX RFu7Ggf9FCsjsiXteQ+xDSolGEtK2a9eBlnCnI9MY3wY2OdOHJlNCpbEjamWVbw3 CwEn4//IWPgFmLcKBD1A9ySYein2tY3CDdNH5fii7ZZ/MNAlL1vuKAVuV30ayQtU V/4xxQXgJ+1JUCPzzKNGMdLs/yumAiLGAs3XzhjUmjVPQWMRWanCOf8dFavDyFG3 4sPS6niMeFUWqM17K0ja7VPVj2QbQQSe34jec93W+zcbnxbWZZuJY9nQ2PsQjRDd /FY0fBQtzopnZMBgRUdYNj09QGuI8kn6dZdD93+/MS2uP95ES7v1nG0bKARrGor7 pNaWlBMeMGI/+bL89SFEQdR52n/uFw== =tTX8 -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Em qua., 21 de jun. de 2023 às 03:33, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > > I tried to use 1.32 again and it only > > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > > greeter.log and x-0.lo. From the log attached below, one difference is > that > > 1.26 starts seat0 and 1.32 does not start it. I got an X session from > 1.26 > > and X does not even start from 1.32. > > In the log there's definitely a bad sign: > > [+69.14s] DEBUG: Got signal 15 from process 1 > [+69.14s] DEBUG: Caught Terminated signal, shutting down > [+69.14s] DEBUG: Stopping display manager > [+69.14s] DEBUG: Display manager stopped > [+69.14s] DEBUG: Stopping daemon > [+69.14s] DEBUG: Exiting with return value 0 > These messages are when I stop lightdm. > > > Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, > the > journal, dmesg...) so we have more information? > I will send some system logs from journalctl when I start and stop lightdm 1.32 and 1.26. > > Also is there something peculiar about your hardware (Nvidia/AMD GPU for > example?) or software (specific configuration or something). > I'm using Nvidia GPU: 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX 1650] (rev a1) And it is using its official drivers: dpkg -l xserver-xorg Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nome Versão Arquitectura Descrição +++-==---= ii xserver-xorg 1:7.7+23 amd64X.Org X server dpkg -l xserver-xorg-video-nvidia Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nome Versão Arquitectura Descrição +++-=---= ii xserver-xorg-video-nvidia 530.41.03-1 amd64NVIDIA binary Xorg driver > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX > RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ > YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy > wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi > NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK > PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 > hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== > =4Egr > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond Using lightdm 1.32 Jun 21 07:49:59 yoda systemd[1]: Starting lightdm.service - Light Display Manager... jun 21 07:49:59 yoda systemd[1]: Started lightdm.service - Light Display Manager. jun 21 07:49:59 yoda audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' jun 21 07:49:59 yoda kernel: audit: type=1130 audit(1687344599.571:939): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' jun 21 07:50:15 yoda systemd[50261]: emacs.service: start operation timed out. Terminating. jun 21 07:50:15 yoda systemd[50261]: emacs.service: Failed with result 'timeout'. jun 21 07:50:15 yoda systemd[50261]: Failed to start emacs.service - Emacs text editor. jun 21 07:50:15 yoda systemd[50261]: emacs.service: Scheduled restart job, restart counter is at 8. jun 21 07:50:15 yoda systemd[50261]: Stopped emacs.service - Emacs text editor. jun 21 07:50:15 yoda systemd[50261]: Starting emacs.service - Emacs text editor... jun 21 07:50:15 yoda emacs[56260]: Warning: due to a long standing Gtk+ bug jun 21 07:50:15 yoda emacs[56260]: https://gitlab.gnome.org/GNOME/gtk/issues/221 jun 21 07:50:15 yoda emacs[56260]: Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost. jun 21 07:50:15 yoda emacs[56260]: Using an Emacs configured with --with-x-toolkit=lucid does not have this problem. jun 21 07:50:15 yoda emacs[56260]: Warning (initialization): Unable to create `user-emacs-directory' (~/.emacs.d/). jun 21 07:50:15 yoda emacs[56260]: Any data that would normally be written there may be lost! jun 21 07:50:15 yoda emacs[56260]: If you never want to see this message again, jun 21 07:50:15 yoda emacs[56260]: customize the variable `user-emacs-directory-warning'. Disable showing Disable logging jun 21 07:50:18 yoda dbus-daemon[50309]: [session uid=33 pid=50309] Failed to activate service 'org.freedesktop.Tracker3.Miner.Files': timed out (service_star
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 01:59 +, solneman33 wrote: > I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and > reinstalled xserver-xorg and xinit. That resolved the issue for me on both > machines. > > I've never reported a bug before, my apologies if this is incorrect > procedure. Well, can you check by reinstalling lightdm 1.32 but making sure you have xserver-xorg? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSnMIACgkQ3rYcyPpX RFs1Hwf9HgLiSwVwW4gMRS2ajXiUXmTRcgNe/jF5libmZllhhKXrMGlq2W/Whf7q 9oIjZ8BYq2x5M3y/VVCH9vYihxFRT6D9Fpg2yw9ojFmJDt0shJuYf2ErJ/2Ymbpy n5JO/1MXtEKbczhmu1ngc23Z9LzOxeuEiZwGJWZoFmhQDlkitD6uOWYByYA4LdA1 W+OsL7tVdE6rUMX9WPJ75mcIgp5+U8mC05Y/pH5+m40/55ZvD1mJotkt4ME6V6f7 fKggPqz8rVZukvXEiTp4oW5CGy/C4zqC5nWiPF8hY8rhZrwpEo9/VFBneEi5Ouze vzSQCUzeQvxMbA1VdXB4EL03t3rt2w== =Fg2s -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > I tried to use 1.32 again and it only > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > greeter.log and x-0.lo. From the log attached below, one difference is that > 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 > and X does not even start from 1.32. In the log there's definitely a bad sign: [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0 Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, the journal, dmesg...) so we have more information? Also is there something peculiar about your hardware (Nvidia/AMD GPU for example?) or software (specific configuration or something). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== =4Egr -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
I was able to reproduce with two of my machines running unstable. xserver-xorg and xinit were removed during the upgrade and I wasn't aware. I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and reinstalled xserver-xorg and xinit. That resolved the issue for me on both machines. I've never reported a bug before, my apologies if this is incorrect procedure. Regards, Sent with [Proton Mail](https://proton.me/) secure email.
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Hi Yves-Alexis, I tried to use 1.32 again and it only generates /var/log/lightdm/lightdm.log. It doesn't generate seat0-greeter.log and x-0.lo. From the log attached below, one difference is that 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 and X does not even start from 1.32. Regards, Adilson Em ter., 20 de jun. de 2023 às 18:13, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote: > > Package: lightdm > > Followup-For: Bug #1038611 > > > > Can't reproduce, starts up just fine for me. > > > > Could you perhaps include the logs from `/var/log/lightdm/´? > > Hi Adilson, > > I'm running 1.32 just fine since it was uploaded to experimental so I can't > reproduce either. Logs would help indeed, and if you can investigate a bit > more on your side (the info about downgrading helps identifying lightdm but > besides that...) > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX > RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF > zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg > D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA > Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3 > 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6 > PKbmA5VO3GjJfl4LABIPkpAwkB+gwg== > =SArv > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=30230 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) [+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ [+0.00s] DEBUG: Monitoring logind for seats [+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Loading users from org.freedesktop.Accounts [+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1004 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1005 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1003 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1002 added [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote: > Package: lightdm > Followup-For: Bug #1038611 > > Can't reproduce, starts up just fine for me. > > Could you perhaps include the logs from `/var/log/lightdm/´? Hi Adilson, I'm running 1.32 just fine since it was uploaded to experimental so I can't reproduce either. Logs would help indeed, and if you can investigate a bit more on your side (the info about downgrading helps identifying lightdm but besides that...) Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6 PKbmA5VO3GjJfl4LABIPkpAwkB+gwg== =SArv -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Package: lightdm Followup-For: Bug #1038611 Can't reproduce, starts up just fine for me. Could you perhaps include the logs from `/var/log/lightdm/´? -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'proposed-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightdm depends on: ii adduser3.134 ii dbus 1.14.8-1 ii debconf [debconf-2.0] 1.5.82 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libgcrypt201.10.2-2 ii libglib2.0-0 2.74.6-2 ii libpam-systemd [logind]252.11-1 ii libpam0g 1.5.2-6 ii libxcb11.15-1 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-3 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+23 Versions of packages lightdm suggests: ii accountsservice 22.08.8-6 ii upower 0.99.20-2 ii xserver-xephyr 2:21.1.7-3 -- debconf information: * shared/default-x-display-manager: gdm3 lightdm/daemon_name: /usr/sbin/lightdm
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Package: lightdm Version: 1.32.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading lightdm to the latest upstream version (1.32.0-2) fails to start X session leading only to console mode. Downgrading to 1.26.0-8, from testing, fixes this bug. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.8 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:p t:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lightdm depends on: ii adduser3.134 ii dbus 1.14.8-1 ii debconf [debconf-2.0] 1.5.82 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libgcrypt201.10.2-2 ii libglib2.0-0 2.74.6-2 ii libpam-systemd [logind]252.11-1 ii libpam0g 1.5.2-6 ii libxcb11.15-1 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-3 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+23 Versions of packages lightdm suggests: ii accountsservice 22.08.8-6 ii upower 0.99.20-2 ii xserver-xephyr 2:21.1.7-3 -- debconf information: * shared/default-x-display-manager: lightdm lightdm/daemon_name: /usr/sbin/lightdm