Bug 2351283 - [Fedora42] : Guest installation is failing for Fedora42!
Summary: [Fedora42] : Guest installation is failing for Fedora42!
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 42
Hardware: ppc64le
OS: All
medium
high
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-11 06:40 UTC by IBM Bug Proxy
Modified: 2025-03-28 06:50 UTC (History)
7 users (show)

Fixed In Version: anaconda-42.27.5-1.fc42
Clone Of:
Environment:
Last Closed: 2025-03-22 02:40:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Installer logs (14.65 KB, application/octet-stream)
2025-03-11 06:41 UTC, IBM Bug Proxy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 211636 0 None None None 2025-03-11 06:41:02 UTC

Description IBM Bug Proxy 2025-03-11 06:40:38 UTC

Comment 1 IBM Bug Proxy 2025-03-11 06:40:51 UTC
== Comment: #0 - Anushree Mathur <Anushree.Mathur2> - 2025-02-20 22:55:32 ==
HOST ENV:
OS : Fedora42 
kernel : 6.14.0-0.rc1.15.fc42.ppc64le
libvirt : 11.0.0
qemu : QEMU emulator version 9.2.0 (qemu-9.2.0-15.fc42)


When I am installing the guest with fedora42, when I am choosing the text mode it is failing as foloows

Starting installer, one moment...
anaconda 42.24-1.fc42 for Fedora 42 (pre-release) started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
 * when reporting a bug add logs from /tmp as separate text/plain attachments

Wayland startup failed, falling back to text mode.
================================================================================
================================================================================
Wayland was unable to start on your machine. Would you like to start an RDP
session to connect to this computer from another computer and perform a
graphical installation or continue with a text mode installation?

1) Use graphical mode via Remote Desktop Protocol
2) Use text mode

Please make a selection from the above ['c' to continue, 'q' to quit, 'r' to
refresh]: 2
Traceback (most recent call last):
  File "/usr/bin/anaconda", line 472, in <module>
    display.setup_display(anaconda, opts)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.13/site-packages/pyanaconda/display.py", line 411, in setup_display
    anaconda.initialize_interface()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/lib64/python3.13/site-packages/pyanaconda/anaconda.py", line 230, in initialize_interface
    self._intf = GraphicalUserInterface(None, self.payload,
                 ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
                                        gui_lock=self.gui_initialized,
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                        fullscreen=False)
                                        ^^^^^^^^^^^^^^^^^
  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.
<sys>:0: DeprecationWarning: builtin type swigvarlink has no __module__ attribute







Pane is dead (status 1, Wed Feb 19 05:43:25 2025)


STEPS to reproduce:
1) Start the guest with fedora42 iso 
2) Use text mode for installation
Expected output :
Installation should proceed and show options

Actual output:
Failing as mentioned above

Installation failing for [Fedora-Server-dvd-ppc64le-42-20250215.n.0.iso]
REFERENCE : https://bugzilla.linux.ibm.com/show_bug.cgi?id=211394

== Comment: #1 - SEETEENA THOUFEEK <sthoufee.com> - 2025-02-21 01:21:29 ==
Based on the reference bug reported in RHEL it should be fixed in  anaconda-40.22.3.22-1.el10. but here we are using 42.24-1.fc42 anaconda version. 

Anu, Can you upload the installer logs so we could mirror to distro and ask suggestion?

== Comment: #2 - Anushree Mathur <Anushree.Mathur2> - 2025-02-24 03:28:44 ==
Hi Seeteena,
I have attached all the installer logs in this zip file!

Comment 2 IBM Bug Proxy 2025-03-11 06:41:05 UTC
Created attachment 2079652 [details]
Installer logs

Comment 3 Jerry James 2025-03-11 15:07:23 UTC
Errr ... and this has something to do with the 0install package how, exactly?

Comment 4 Jerry James 2025-03-12 17:14:26 UTC
Hello?  IBM people?  Your automatic bug filer has automatically filed a bug against the wrong Fedora component.  Please fix your bug filer and change the component on this bug.

Also, the external bug link above points to https://bugzilla.linux.ibm.com/show_bug.cgi?id=211636, but according to my ISP, the name bugzilla.linux.ibm.com is not resolvable.  Is there a valid DNS name that should be used instead?

Comment 5 IBM Bug Proxy 2025-03-14 08:13:37 UTC
------- Comment From Anushree.Mathur2 2025-02-20 23:55 EDT-------

------- Comment From sthoufee.com 2025-02-21 02:21 EDT-------

------- Comment From sthoufee.com 2025-03-14 04:06 EDT-------
(In reply to comment #7)
> Hello?  IBM people?  Your automatic bug filer has automatically filed a bug
> against the wrong Fedora component.  Please fix your bug filer and change
> the component on this bug.
>
> Also, the external bug link above points to
> https://bugzilla.linux.ibm.com/show_bug.cgi?id=211636, but according to my
> ISP, the name bugzilla.linux.ibm.com is not resolvable.  Is there a valid
> DNS name that should be used instead?

Changed the component to Anaconda.

Comment 6 Jiri Konecny 2025-03-14 14:04:24 UTC
Most probably we need to backport this fix:
https://github.com/rhinstaller/anaconda/pull/6239

Comment 7 Fedora Update System 2025-03-21 12:49:15 UTC
FEDORA-2025-a50e6b787b (anaconda-42.27.5-1.fc42 and anaconda-webui-28-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a50e6b787b

Comment 8 Fedora Update System 2025-03-22 02:40:02 UTC
FEDORA-2025-a50e6b787b (anaconda-42.27.5-1.fc42 and anaconda-webui-28-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 IBM Bug Proxy 2025-03-28 06:50:25 UTC
------- Comment From Anushree.Mathur2 2025-03-28 02:42 EDT-------
Kernel : 6.14.0-0.rc7.56.fc42.ppc64le
qemu : QEMU emulator version 9.2.2 (qemu-9.2.2-2.fc42)
libvirt : libvirtd (libvirt) 11.0.0

For the guest I have used this fedora iso Fedora-Server-dvd-ppc64le-42_Beta-1.4.iso, now the installation for the guest is going on without any failure! This issue has been fixed.

Here is my analysis:

Starting sshd-keygen -?penSSH rsa Server Key Generation...
Starting systemd-logind.service - User Login Management...
[  OK  ] Finished anaconda-import-initramfs?fs stage of Anaconda via kickstart.
[  OK  ] Finished anaconda-nm-config.servic?conda NetworkManager configuration.
[  OK  ] Finished dracut-shutdown.service - Restore /run/initramfs on shutdown.
^[[1;3R^[[60;106RStarting installer, one moment...
anaconda 42.27.3-1.fc42 for Fedora 42 (pre-release) started.

Please make a selection from the above ['c' to continue, 'q' to quit, 'r' to
refresh]: 2
================================================================================
================================================================================
Installation

1) [x] Language settings                 2) [x] Time settings
(English (United States))                (America/New_York timezone)
3) [!] Installation source               4) [!] Software selection
(Setting up installation                 (Processing...)
source...)
5) [!] Installation Destination          6) [x] Network configuration
(Processing...)                          (Connected: enp0s1)
7) [!] Root password                     8) [!] User creation
(Root account is disabled)               (No user will be created)

Please make a selection from the above ['b' to begin installation, 'q' to quit,
'r' to refresh]:

Thanks for fixing this.


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