Today, running the release validation tests for the new iso F39 beta 1.1 (Fedora-Budgie-Live-x86_64-39_Beta-1.1.iso) cannot start the installation clicking on the icons (both at desktop, and at the menu). When I open a terminal and run the comand "liveinst" then anaconda starts correctly and I can install F39 budgie. I tested tha last F38 respin too (F38-WORK-x86_64-LIVE-20230901.iso), and it works perfectly. Reproducible: Always Steps to Reproduce: 1.start live session 2.try to install by clicking on the "install do HD" icons 3.wait Actual Results: nothing happens Expected Results: anaconda GUI starts and we can go throught the installation processes as usual. Static hostname: F39-Budgie Icon name: computer-vm Chassis: vm 🖴 Machine ID: 803e2378bb0543479cf1fccdf2c2b620 Boot ID: ba4293953ab34fbaabda7818abedb0a3 Virtualization: kvm Operating System: Fedora Linux 39 (Budgie Prerelease) CPE OS Name: cpe:/o:fedoraproject:fedora:39 OS Support End: Tue 2024-05-14 OS Support Remaining: 7month 4w 2d Kernel: Linux 6.5.2-301.fc39.x86_64 Architecture: x86-64 Hardware Vendor: QEMU Hardware Model: Standard PC _Q35 + ICH9, 2009_ Firmware Version: edk2-20230524-3.fc38 Firmware Date: Wed 2023-05-24 Firmware Age: 3month 3w abrt-desktop-2.17.1-3.fc39.x86_64 budgie-desktop-10.8-1.fc39.x86_64 budgie-desktop-defaults-0.5.1-1.fc39.noarch budgie-desktop-view-1.2.1-2.fc39.x86_64 cinnamon-desktop-5.8.0-2.fc39.x86_64 desktop-backgrounds-budgie-39.0.0-3.fc39.noarch desktop-backgrounds-compat-39.0.0-3.fc39.noarch desktop-backgrounds-gnome-39.0.0-3.fc39.noarch desktop-file-utils-0.26-9.fc39.x86_64 gnome-desktop3-44.0-7.fc39.x86_64 gnome-remote-desktop-45.beta-1.fc39.x86_64 gsettings-desktop-schemas-45~beta-1.fc39.x86_64 mate-desktop-libs-1.26.1-4.fc39.x86_64 open-vm-tools-desktop-12.1.5-4.fc39.x86_64 sound-theme-freedesktop-0.8-20.fc39.noarch xdg-desktop-portal-1.17.0-2.fc39.x86_64 xdg-desktop-portal-gtk-1.14.1-3.fc39.x86_64 ################################################# Tested F38 respin and it works fine: abrt-desktop-2.17.1-1.fc38.x86_64 budgie-desktop-10.8-1.fc38.x86_64 budgie-desktop-defaults-0.4-1.fc38.noarch budgie-desktop-view-1.2.1-1.fc38.x86_64 cinnamon-desktop-5.8.0-1.fc38.x86_64 desktop-backgrounds-compat-38.0.0-2.fc38.noarch desktop-backgrounds-gnome-38.0.0-2.fc38.noarch desktop-file-utils-0.26-8.fc38.x86_64 gnome-desktop3-44.0-1.fc38.x86_64 gnome-remote-desktop-44.2-1.fc38.x86_64 gsettings-desktop-schemas-44.0-1.fc38.x86_64 mate-desktop-libs-1.26.1-3.fc38.x86_64 open-vm-tools-desktop-12.1.5-3.fc38.x86_64 sound-theme-freedesktop-0.8-19.fc38.noarch xdg-desktop-portal-1.16.0-3.fc38.x86_64 xdg-desktop-portal-gtk-1.14.1-2.fc38.x86_64
Created attachment 1988698 [details] print from a journalctl -f session running when I try to install This is what is logged at the moment I click on any of the icons "install on hard drive" I'm running the live iso on a UEFI VM, created using virtmanager on a F38 KDE host.
Created attachment 1988700 [details] live iso anaconda.log
Created attachment 1988702 [details] live iso dbus.log
Created attachment 1988703 [details] live iso packaging.log
Created attachment 1988704 [details] live iso program.log
Created attachment 1988705 [details] live iso storage.log
Was able to reproduce in virt-manager and live ISO on laptop. Added relevant logs from it.
Yes, also happens running usb live-iso on baremetal Acer Aspire Intel® Core™ i7-3632QM CPU
Proposed as a Freeze Exception for 39-beta by Fedora user geraldosimiao using the blocker tracking app because: If this happens on a release-blocking desktop it would surely be a blocker bug, because users can't install by clicking on the "install to hard drive" icon at desktop. But, because this is happening on Budgie desktop it can be a FE.
Issue identified in Anaconda and a MR has been submitted by halfline: https://github.com/rhinstaller/anaconda/pull/5171 May impact other desktops as well, but confirmed removal of exec fixes it for Budgie Desktop at the very least.
+3 in https://pagure.io/fedora-qa/blocker-review/issue/1308 , marking accepted. We'll pull this in somehow if another candidate is necessary.
F39 port PR: https://github.com/rhinstaller/anaconda/pull/5175
As it looks like the Beta candidate we already have may be approved, let's flag this commonbugs so we can at least document the workaround for folks if we release this way.
edited the common issue on discussion https://discussion.fedoraproject.org/t/new-proposed-common-issue-found-unable-to-start-installation-of-f39-budgie-beta-1-1-clicking-on-the-desktop-or-menu-icon/89883
Created attachment 1989061 [details] Bug affect fedora 39 SWAY too - screenshot Bug affect sway desktop install too (Fedora-Sway-Live-x86_64-39_Beta-1.1.iso) when we try to install by the sugested method (pressing win+d and typing liveinst) it does not install. Workaround is the same as budgie, open a terminal (win+enter) and typing liveinst.
Created attachment 1989062 [details] screenshot SWAY installation workaround At SWAY live-session after running liveinst on the terminal, anaconda starts. Then just use win+f to go fullscreen and proceed the installation.
FEDORA-2023-7aa321caa4 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7aa321caa4
FEDORA-2023-7aa321caa4 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-7aa321caa4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7aa321caa4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Great, tested the new anaconda-39.32.3-1.fc39 on both budgie beta 1.1 and sway beta 1.1 and bug is fixed on both. Anaconda now starts correctly by clicking on the icon (budgie) or following the instructions on sway desktop (win+d and typing liveinst).
I thought this anaconda upgrade could help fix this bug at SOAS too, but it didn't. Something else must be happening at SOAS installation. https://bugzilla.redhat.com/show_bug.cgi?id=2239137
FEDORA-2023-7aa321caa4 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.