Inital-setup crashes, resulting in anaconda never starting, and the system never getting setup Reproducible: Always Steps to Reproduce: 1.Download F42 aarch64 raw.xz installer image 2.Write Image to SD Card 3.Boot rPi400 from SD Card Actual Results: Machine boots, but never goes into anaconda, but instead takes you directly to sddm, with no root user, no users, and no other setup Expected Results: Installer brings up Anaconda, in order to do initial setup, for users, passwords, timezone, network, etc. From the system journal: Apr 11 13:43:57 fedora initial-setup[1126]: initializing GUI Apr 11 13:43:57 fedora initial-setup[1126]: Initial Setup crashed due to unhandled exception: Traceback (most recent call last): File "/usr/libexec/initial-setup/initial-setup-graphical", line 13, in <module> is_instance.run() ~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/initial_setup/__init__.py", line 427, in run ui = initial_setup.gui.InitialSetupGraphicalUserInterface() File "/usr/lib/python3.13/site-packages/initial_setup/gui/gui.py", line 20, in __init__ GraphicalUserInterface.__init__(self, None, None, get_product_title, is_final(), ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ quitDialog=InitialSetupQuitDialog) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.13/site-packages/pyanaconda/ui/gui/__init__.py", line 530, in __init__ self.mainWindow = MainWindow(fullscreen=fullscreen, decorated=False) ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.13/site-packages/pyanaconda/ui/gui/__init__.py", line 290, in __init__ super().__init__() ~~~~~~~~~~~~~~~~^^ File "/usr/lib64/python3.13/site-packages/gi/overrides/Gtk.py", line 505, in __init__ raise RuntimeError( "Gtk couldn't be initialized. " "Use Gtk.init_check() if you want to handle this case.") RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to handle this case.
Created attachment 2084517 [details] Full output from journalctl
Sorry, I forgot to add, this is the LXQt spin raw.xz image.
This problem persists with Fedora 43 XFCe and LXQt raw image spins. After using either RpiImager or Fedora Media Writer to prepare XFCe and LXQt installation media with Samsung flash card, inserted into RPI400 and booted Linux. The greeting screen of LXQt advises to select a username and password; but, is unresponsive to keyboard entry. The greeting screen of XFCe prompts to select a user, and enter a password, which are, of course unspecified and unknown.
Please note: this problem effects all ARM Spins: XFCE, LXQT, and COSMIC. This means all ARM Spins cannot be used without the initial-setup script being run at first boot. Is a fix planned for this bug? This is a duplicate of a prior bug from 11 months ago: https://bugzilla.redhat.com/show_bug.cgi?id=2358688
For F44 this makes initial-setup working sed -i 's/x11/wayland/g' /usr/libexec/initial-setup/initial-setup-graphical
It has been confirmed that the fix using sed in my custom F44 image causes initial-setup to run.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Custom LXQt images with fixed initial-setup https://sourceforge.net/projects/fedora-remix-images/files/releases/44/LXQT/aarch64/
(In reply to nucleo from comment #6) > It has been confirmed that the fix using sed in my custom F44 image causes > initial-setup to run. The change suggested in comment 5: sed -i 's/x11/wayland/g' /usr/libexec/initial-setup/initial-setup-graphical Basically changes the GDK_BACKEND env var from "x11" to "wayland" in the code: #!/usr/bin/python3 import os from initial_setup import InitialSetup, InitialSetupError # Doesn't work with native Wayland yet os.environ["GDK_BACKEND"] = "x11" is_instance = InitialSetup(gui_mode=True) try: is_instance.run() except InitialSetupError: # Initial Setup with graphical interface apparently failed exit(1) # check if we should reboot the machine instead of continuing to # the login screen if is_instance.reboot_on_quit: os.system("reboot") # Initial Setup with graphical interface completed successfully exit(0) This line: os.environ["GDK_BACKEND"] = "x11" becomes: os.environ["GDK_BACKEND"] = "wayland" Is this the only change you did on your custom image, or was there also something else ? I have tried the same patch on AARCH64 xfce with the default initial-setup-gui-wayland-generic package (which uses weston) installed and it did not help. But when I installed initial-setup-gui-wayland-miriway instead (it is mutually exclusive with initial-setup-gui-wayland-generic), which uses something called "miriway" as a compositor instead of weston & then used: os.environ["GDK_BACKEND"] = "wayland" the Initial Setup GUI would finally launch successfully. This was suggested by you in comment 18 of https://bugzilla.redhat.com/show_bug.cgi?id=2358688. So is your custom LXQT image also using miriway or does the weston using initial-setup-gui-wayland-generic work with just GDK_BACKEND set to "wayland" ?
On this LXQt image already installed initial-setup-gui-wayland-miriway https://dl.fedoraproject.org/pub/fedora/linux/releases/44/Spins/aarch64/images/Fedora-LXQt-Disk-44-1.7.aarch64.raw.xz Install sddm-wayland-miriway-0:26.01-1.fc44.noarch Group 833a0dd04d70449da08df04ebbabe4b8 Install lxqt-wayland-session-default-compositor-miriway-0:0.3.2-1.fc44.noarch Group 833a0dd04d70449da08df04ebbabe4b8 Install miriway-0:26.01-1.fc44.aarch64 Dependency 833a0dd04d70449da08df04ebbabe4b8 Install lxqt-miriway-session-0:0.3.2-1.fc44.noarch Dependency 833a0dd04d70449da08df04ebbabe4b8 Install mir-common-libs-0:2.25.1-5.fc44.aarch64 Dependency 833a0dd04d70449da08df04ebbabe4b8 Install mir-server-libs-0:2.25.1-5.fc44.aarch64 Dependency 833a0dd04d70449da08df04ebbabe4b8 Install initial-setup-gui-wayland-miriway-0:26.01-1.fc44.noarch Dependency 833a0dd04d70449da08df04ebbabe4b8 So 'os.environ["GDK_BACKEND"] = "wayland"' is enough to make initial-setup work on this image.
My custom remix also includes other changes, but they are not related to the initial-setup startup failure.