4.3.2 Graphical setup not launching at first boot

First, a big thank you to the team for bringing 4.3.2 release !

There seems to be a new occurrence of an issue with first boot graphical setup not lauching automatically after a fresh install from 4.3.2 ISO (Hardware : Dell XPS 9520 - 64GB RAM, GPT/UEFI partition scheme).

After first boot, unlocking LUKS and logging to Qubes, only almost empty menus are available, graphical setup to install initial templates is not starting automatically.

Not a major issue as running “sudo /usr/libexec/initial-setup/initial-setup-graphical” from dom0 termnial works correctly, however this may affect new users.

Hi michel - and welcome to the forum.

Can you share what is written to the terminal, when you run the initial-setup-graphical?

:slight_smile:

Oh - wait .. when running it from a dom0 terminal works, the question is “why did the frame buffer device not work on the first start” (iirc) .. and that is not part of the log from running it in the dom0 terminal .. so nothing to see here – move along .. don’t mind me .. :wink:

:slight_smile:

No problem. Indeed starting manually works fine.

I can see in anaconda/syslog that systemctl enable initial-setup.service --root /mnt/sysroot returned code 0, seems OK at this stage.

Not sure how to find in initial installation logs (first boot) why it didn’t launch.

Can you find something from journalctl, looking for something like run-initial-setup and a coredump after it?

Here it is, no coredump but it seems it couldn’t find the display ( failed to create compositor backend )

Not sure it can be hardware related, the laptop is a machine with discrete GPU (embedded Intel + nvidia GPU), however the rest of the system seems to have no issue with access to graphical interface.

Oct 07 08:51:22 dom0 systemd[1]: Started session-4.scope - Session 4 of User root.
Oct 07 08:51:22 dom0 audit[3573]: USER_START pid=3573 uid=0 auid=0 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd acct="root" exe="/usr/lib/systemd/systemd-executor" hostname=dom0 addr=? terminal=/dev/tty7 res=success'
Oct 07 08:51:22 dom0 initial-setup[3581]: Starting Initial Setup GUI
Oct 07 08:51:22 dom0 run-initial-setup[3603]: Date: 2026-10-07 CEST
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.437] weston 14.0.1
Oct 07 08:51:22 dom0 run-initial-setup[3603]: ``https://wayland.freedesktop.org
Oct 07 08:51:22 dom0 run-initial-setup[3603]: Bug reports to: ``https://gitlab.freedesktop.org/wayland/weston/issues/
Oct 07 08:51:22 dom0 run-initial-setup[3603]: Build: 14.0.1
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.437] Command line: weston --config=/tmp/tmp.wNZhFSIROz-wl-weston-firstboot-ini --socket=wl-firstboot-0 --drm-device=card0 --additional-devices=card1,
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.437] OS: Linux, 6.18.51-1.qubes.fc41.x86_64, #1 SMP PREEMPT_DYNAMIC Sat Sep 12 20:19:12 UTC 2026, x86_64
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.437] Flight recorder: enabled
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.437] Using config file '/tmp/tmp.wNZhFSIROz-wl-weston-firstboot-ini'
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.438] Output repaint window is 7 ms maximum.
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.438] Loading module '/usr/lib64/libweston-14/drm-backend.so'
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.439] initializing drm backend
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.439] Trying libseat launcher...
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.439] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.439] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.441] [libseat/libseat.c:73] Seat opened with backend 'logind'
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.441] libseat: session control granted
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.444] ERROR: DRM device 'card0' is not a KMS device.
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.444] no drm device found
Oct 07 08:51:22 dom0 run-initial-setup[3603]: [08:51:22.493] fatal: failed to create compositor backend
Oct 07 08:51:22 dom0 run-initial-setup[3603]: Internal warning: debug scope 'drm-backend' has not been destroyed.
Oct 07 08:51:22 dom0 initial-setup[3608]: Initial Setup finished successfully, disabling
Oct 07 08:51:22 dom0 systemctl[3611]: Removed '/etc/systemd/system/graphical.target.wants/initial-setup.service'.
Oct 07 08:51:22 dom0 systemctl[3611]: Removed '/etc/systemd/system/multi-user.target.wants/initial-setup.service'.

This looks very related. Can you open an issue on github, with output of udevadm info -q all -n dri/card0 (and same for card1, just in case)?

Done, see issue #11181.

Thank you!