Fedora Account System
Red Hat Associate
Red Hat Customer
After booting up a live iso I selected the install to hard drive option. Afterwards the install doesn't start. I opened a terminal and started liveinst, which hangs without any error. I started anaconda --liveinst --graphical, but it crashed with an unexpected exception. I rebooted and this time I selected Troubleshooting which booted nicely on a single monitor and the install shown up, but on a single monitor. I wanted to switch to UEFI boot at this point to see if it can solve anything, but Fedora Workstation 39 ISO and Fedora Everything 39 wasn't able to use UEFI, it just wrote a bunch of errors. So I returned to the workaround I found and completed an install, but I am not happy with that because after the install I have a single monitor environment. How can I fix UEFI and liveinst to work? Reproducible: Always Steps to Reproduce: 1.Boot Fedora Workstation 39 live ISO 2.Start installer 3.Installer doesn't show up Actual Results: Using troubleshooting in the boot options I was able to install a single monitor environment Expected Results: UEFI boot and liveinst works out of the box
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
I’m on a laptop without any external monitor. This is exactly the error I get: root@localhost-live:/home/liveuser# liveinst ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2505): WARNING **: 20:27:44.777: expected enumeration type void, but got PyBlockDevPlugin instead Starting installer, one moment... ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead ** (process:2607): WARNING **: 20:27:47.096: expected enumeration type void, but got PyBlockDevPlugin instead anaconda 39.32.6-2.fc39 for Fedora 39 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 Traceback (most recent call last): File "/sbin/anaconda", line 333, in <module> startup_utils.live_startup() File "/usr/lib64/python3.12/site-packages/pyanaconda/startup_utils.py", line 358, in live_startup inhibit_screensaver() File "/usr/lib64/python3.12/site-packages/pyanaconda/screensaver.py", line 96, in inhibit_screensaver inhibit_id = session_proxy.Inhibit("anaconda", "Installing") ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 161, in __getattr__ member = self._get_member(self._get_interface(name), name) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 211, in _get_interface self._handler.specification.members ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 212, in specification self._specification = self._get_specification() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 332, in _get_specification xml = self._call_method( ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 435, in _call_method self._message_bus.connection, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 169, in connection self._connection = self._get_connection() ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 336, in _get_connection return self._provider.get_session_bus_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 67, in get_session_bus_connection return Gio.bus_get_sync( ^^^^^^^^^^^^^^^^^ gi.repository.GLib.GError: g-io-error-quark: Error sending credentials: Error sending message: Broken pipe (44) It is not clear to me whether I’m reporting the same issue as above. Peter, could you check whether your issue is caused by the same error? I was trying to install Fedora 39 LXDE and I wonder whether anaconda has issues with xscreensaver.
To check whether the issue has been fixed for the coming Fedora 40, I downloaded and tested https://dl.fedoraproject.org/pub/fedora/linux/development/40/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-40-20240217.n.0.iso. I’m afraid I get exactly the same error message: root@localhost-live:/home/liveuser# liveinst Starting installer, one moment... anaconda 40.22.1-1.fc40 for Fedora 40 (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 Traceback (most recent call last): File "/sbin/anaconda", line 348, in <module> startup_utils.live_startup() File "/usr/lib64/python3.12/site-packages/pyanaconda/startup_utils.py", line 360, in live_startup inhibit_screensaver() File "/usr/lib64/python3.12/site-packages/pyanaconda/screensaver.py", line 96, in inhibit_screensaver inhibit_id = session_proxy.Inhibit("anaconda", "Installing") ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 161, in __getattr__ member = self._get_member(self._get_interface(name), name) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 211, in _get_interface self._handler.specification.members ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 212, in specification self._specification = self._get_specification() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 332, in _get_specification xml = self._call_method( ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 435, in _call_method self._message_bus.connection, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 169, in connection self._connection = self._get_connection() ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 336, in _get_connection return self._provider.get_session_bus_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 67, in get_session_bus_connection return Gio.bus_get_sync( ^^^^^^^^^^^^^^^^^ gi.repository.GLib.GError: g-io-error-quark: Error receiving data: Connection reset by peer (44) Since the issue prevents the graphical installation of new Fedora versions, would it be possible to have someone to check this?
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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 39 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.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.