Bug 2359195 - initial-setup fails on LXQt aarch64 raw.xz installation image -- rPi400
Summary: initial-setup fails on LXQt aarch64 raw.xz installation image -- rPi400
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: 44
Hardware: aarch64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-11 22:32 UTC by Shawn W Dunn
Modified: 2026-05-06 12:52 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
Full output from journalctl (493.59 KB, text/plain)
2025-04-11 22:34 UTC, Shawn W Dunn
no flags Details

Description Shawn W Dunn 2025-04-11 22:32:56 UTC
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.

Comment 1 Shawn W Dunn 2025-04-11 22:34:09 UTC
Created attachment 2084517 [details]
Full output from journalctl

Comment 2 Shawn W Dunn 2025-04-11 22:34:43 UTC
Sorry, I forgot to add, this is the LXQt spin raw.xz image.

Comment 3 Alan B Saichek 2026-01-02 17:56:36 UTC
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.

Comment 4 sk8board 2026-03-08 15:26:52 UTC
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

Comment 5 nucleo 2026-04-29 23:51:42 UTC
For F44 this makes initial-setup working

sed -i 's/x11/wayland/g' /usr/libexec/initial-setup/initial-setup-graphical

Comment 6 nucleo 2026-05-05 16:58:02 UTC
It has been confirmed that the fix using sed in my custom F44 image causes initial-setup to run.

Comment 7 Fedora Release Engineering 2026-05-06 12:34:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.