Your message dated Thu, 10 Jul 2025 23:21:52 +0200
with message-id <9cb10b40c222767c084a90208f5fd...@it-yourself.at>
and subject line Bug#1108976: Closing – not a bug in live-build
has caused the Debian Bug report #1108976,
regarding live-config: Graphical Live-System with Cinnamon fails to start
properly under Trixie, works under Bookworm (regression)
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.)
--
1108976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-config
Version: 20250505 (Package live-build)
Severity: normal
X-Debbugs-Cc: <daniel.ge...@it-yourself.at>
Dear Debian Live team,
I would like to report a regression in the behavior of graphical Debian
Live systems when built with live-build under Debian 13 (Trixie),
compared to Debian 12 (Bookworm).
A graphical live system (using Cinnamon and LightDM) that was fully
functional under Bookworm fails to start the graphical session under
Trixie — even with the exact same configuration, package list, and build
structure.
## Setup:
- Live system built with live-build using the following package
selection:
live-boot
live-config
live-config-systemd
systemd-sysv
lightdm
lightdm-gtk-greeter
cinnamon-desktop-environment
network-manager
network-manager-gnome
xserver-xorg
xinit
calamares
calamares-settings-debian
task-german-desktop
task-german
locales
Content of /auto/config
#!/bin/sh
set -e
lb config noauto \
--architecture amd64 i386 \
--distribution trixie \
--mirror-bootstrap http://ftp.at.debian.org/debian/ \
--mirror-binary http://ftp.at.debian.org/debian/ \
--bootappend-live "boot=live components locales=de_AT.UTF-8
keyboard-layouts=de" \
--debian-installer none \
--interactive shell \
--archive-areas "main contrib non-free non-free-firmware" \
"${@}"
- No autologin is configured
- A user is correctly created by live-config (confirmed)
- LightDM is installed and enabled
- However, the system boots to a TTY login prompt instead of showing the
graphical login
## Notes:
- On the **same hardware**, a Bookworm-based image with identical
configuration **boots fine into LightDM** and starts the Cinnamon
desktop correctly.
- On Trixie, LightDM fails to launch the graphical session.
- Nouveau fails to initialize properly on some modern NVIDIA GPUs (e.g.
RTX 3080).
- This was not required in Bookworm for the same hardware.
## Additional note:
Installing `xinit` alone (without any manual `.xinitrc` configuration)
allows the system to successfully start Cinnamon from the console via
`startx`.
This confirms that X11 and the Cinnamon session are fully functional and
properly installed. The graphical session only fails when starting via
LightDM, which suggests a misconfiguration or missing default
integration between LightDM and the Cinnamon session in the current live
setup, I assume.
## Conclusion:
There appears to be a behavioral regression in the combination of
live-config and/or live-build under Trixie:
- Either any of the DMs are not being configured properly during live
system creation (tested lightdm, sddm)
- Or the greeter/session integration is incomplete?
- Or X11 startup fails silently on some hardware?
- Or the debian live build environment has to be used in a different way
for trixie?
Btw. when installing Trixie with the RC1 Installer, there is no such
problem as mentioned above, which leads me to the conclusion that
something in the live-build-environment has changed, or is not working
properly at the moment.
Please advise whether this change is intentional, and if not, whether
Debian Live is expected to function out-of-the-box for graphical
sessions under Trixie as it did under Bookworm.
Best regards,
Daniel Gestl
--- End Message ---
--- Begin Message ---
Hi,
I’m closing this bug as it is not a bug in live-build itself.
The described issue occurs in system built with "live-build" and
installed with calamares installert after installing the proprietary
NVIDIA driver. After rebooting, the graphical login manager (e.g., SDDM
or LightDM) does not start properly.
sddm goes into a blackscreen.
lightdm drops back to tty.
After disabling the lightdm.service (autostart) I am able to start it
successfully and manual from console.
sddm also works if started manually from console, not when autostarting.
This appears to be a race condition between the NVIDIA driver
initialization and the login manager startup — not a problem caused by
live-build or live-config directly.
While this may be worth documenting somewhere (e.g., in the live-build
manual or FAQ), I don’t believe live-build itself is at fault.
Thanks for your work!
--- End Message ---
