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
Processed: Re: Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot
Processing control commands: > forwarded -1 https://github.com/canonical/lightdm/issues/70 Bug #1038701 [lightdm] lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot Set Bug forwarded-to-address to 'https://github.com/canonical/lightdm/issues/70'. -- 1038701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forwarded -1 https://github.com/canonical/lightdm/issues/70 On Tue, 2023-06-20 at 12:44 +0300, Yura wrote: > Dear Maintainer, > > I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to > locate daemon control file" error message from lightdm, which indicates that > there is some issue. > > Nevertheless, the booting process succeeds. > > The expectation is that such error shouldn't occur. Hey, this looks to be https://github.com/canonical/lightdm/issues/70 but there's not definite conclusion in that issue. It looks like gnome-keyring is launched for the lightdm user but lacks space to write some files. I don't think we really need gnome-keyring as part of the lightdm session anyway so I don't think it's really problematic, mostly cosmetic at that point. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSGOMACgkQ3rYcyPpX RFu2mwgAtSXk2CbNNaPObACSEhVIbL3uZYFPMDyHucZQ2vXYYp/occiOlAaf1rNF efANrjxSFNngBuGrGvWyki5uGyw14GHKudSb4KJgg6qMbW4meCES4cvf/m6VP+p8 Is2Vbj6Dk4c3c0+JEZyWJD6Me9h6nMhu1g4RAyrxPo3K6kzbmcsWx2ZzAr3Yo686 NyrEy0jdBuea/C/eBh4q+fFNVB6BnXkwLBDYd0vHes/V3lfxAxG9Wv08L47B5elP ixr2pfX0Bx6h4thaloj8C88PR2sDNgGM95CJHktxKxX7By8tEp8yIKQg7x/NnR6D IoN3d/HUQFqbJYz+A8iiYKsgK9EsNw== =6fHb -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 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#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot
Package: lightdm Version: 1.26.0-8 Severity: minor X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com Dear Maintainer, I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to locate daemon control file" error message from lightdm, which indicates that there is some issue. Nevertheless, the booting process succeeds. The expectation is that such error shouldn't occur. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled DE: Xfce Versions of packages lightdm depends on: ii adduser3.134 ii dbus 1.14.6-1 ii debconf [debconf-2.0] 1.5.82 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libgcrypt201.10.1-3 ii libglib2.0-0 2.74.6-2 ii libpam-systemd [logind]252.6-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-2+b1 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-4 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 pn xserver-xephyr -- Configuration Files: /etc/lightdm/lightdm.conf changed: [LightDM] [Seat:*] greeter-hide-users=false [XDMCPServer] [VNCServer] -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm
