Hi, Roland Clobus <rclobus@rclobus.nl> (2024-12-24): > On 24/12/2024 18:58, Cyril Brulebois wrote: > > Maybe you could be more specific? That's rather vague and if I look > > into live-build-install_to_HD_with_di, I see d-i starting, except in > > text mode. > > That is my point. It does not start the graphical mode, like it did the > day before. OK, I wasn't sure I was looking at the right place. > > On the d-i side, if the graphical installer fails to start, we get X > > starting in a loop (see recent bug reports until the fix in the X > > server), there's no fallback to text mode. > > > > Without any more information, that looks like some live problem… > > The live installer runs 'daily-build' from the debian-installer > repository. The generated initrd.gz was then started with qemu: > > kvm -kernel build/dest/cdrom/gtk/vmlinuz -initrd > build/dest/cdrom/gtk/initrd.gz -m 2G Ah, some details, thanks. Trying that with today's files just works for me (the graphical installer starts): https://d-i.debian.org/daily-images/amd64/20241224-01:42/cdrom/gtk/ Building with daily-build seems super slow for no obvious reasons, so I've just tried a regular `dpkg-buildpackage -b` instead, and I can replicate the issue with files below build/dest/cdrom/gtk after the build. With cdebconf udebs reverted to their testing version (changing only that, feeding them via localudebs after deb-reversion), the problem goes away. Paging Colin and Gioele accordingly. Thanks for the heads-up. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature