Your message dated Fri, 06 Oct 2023 23:11:09 +0200
with message-id <f371e986f56617f222adcced1ff812f40f6400fa.ca...@debian.org>
and subject line Re: Bug#1038611: Help with investigating a bug in the
LightDM/logind/DDX stack
has caused the Debian Bug report #1038611,
regarding lightdm 1.32 fails to start X on nvidia binary driver
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1038611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 adduser 3.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 libgcrypt20 1.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 libxcb1 1.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
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Thu, 2023-10-05 at 22:55 -0300, Adilson dos Santos Dantas wrote:
> But this module was not loaded at boot time and I found an old nvidia.conf
> at /etc/modprobe.d. Probably it was from an old nvidia package and it
> prevented this module from loading..
>
> I removed this file and finally nvidia_drm was loaded in the next boot. It
> worked with lightdm and with sddm. With sddm it stopped working for more
> than one year until I removed nvidia.conf from modprobe.d.
>
> Then, for me, the root cause is a nvidia_drm module not loaded due to a file
> in modprobe.d . I don't know if there is something similar with the
> RasperryPi 4.
>
Ok, thanks for the investigation, that's good to know. So it looks like an
issue isolated to your box (and maybe Steev test box) and not a general one.
I'm closing the bug on those grounds, feel free to reopen if needed.
And hopefully the bug will serve as documentation in case other people
experience that.
Have a nice day.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUgd+0ACgkQ3rYcyPpX
RFv9gggA2c+vR8Kpd3tUHPWmJI5YdhlXatkRHDydiLsNKQrLxxTdoCvKSdNTsAeW
r72EesXtzJkRD4Z5FanIETPW9SF/e6s9Rv7iFhbhI6R17FLLE7/lqtr9jA9W4lLB
u3iRSyHz5s0TpiKn98t696Fm4m2F0PA1Uqd6cGgEyBacQXNCHd8Z2zEWEEwPK6n6
evWs95HO0Lq8Y+qLae6fxJevhfXtnZNB25sL2xo3sqRi10lKI44VAtpAiq9zd5l8
zBp7h/bNpQXFKyndm5xKsxB1LjNppFTwhRkSwJMmipkJyEwabRh3vs7QeapkRFd5
JfevfeLD8CLLKSzFqshuyK6PZ0hasw==
=KCFo
-----END PGP SIGNATURE-----
--- End Message ---
