Hide Forgot
Description of problem: GLib assert fires during installation. Version-Release number of selected component (if applicable): anaconda 26.2-1 How reproducible: Steps to Reproduce: 1. Configure DHCP+TFTP server (I used dnsmasq). 2. In TFTP-served directory run: u=https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/aarch64/os/ wget -N $u/EFI/BOOT/grubaa64.efi $u/images/pxeboot/vmlinuz $u/images/pxeboot/initrd.img echo "linux (tftp)/vmlinuz ip=enp1s0f0:dhcp ksdevice=enp1s0f0 inst.repo=$u initrd (tftp)/initrd.img boot" > grub.cfg 3. Network boot target system and monitor its serial console. Actual results: * installation log files are stored in /tmp during the installation * shell is available on TTY2 * if the graphical installation interface fails to start, try again with the inst.text bootoption to start text installation * when reporting a bug add logs from /tmp as separate text/plain attachments19:54:01 X startup failed, falling back t o text mode=========================================================================================================== =====================================================VNCX was unable to start on your machine. Would you like to star t VNC to connect to this computer from another computer and perform a graphical installation or continue with a text mode installation? 1) Start VNC 2) Use text mode Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]: [anaconda]1:main* 2:shell 3:log 4:storage-log >Switch tab: Alt+Tab | Help: F1 [anaconda]1:main* 2 :shell 3:log 4:storage-log >Switch tab: Alt+Tab | Help: F1 2 (process:1829): GLib-GIO-CRITICAL **: g_dbus_connection_call_sync_internal: assertion 'object_path != NULL && g_varian t_is_object_path (object_path)' failed Expected results: No GLib assert Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.