Description of problem: Anaconda will not start upon click on install to hard drive or clicking on the taskbar icon. Version-Release number of selected component (if applicable): Fedora 37 Rawhide 20220621.n.3 Base How reproducible: Steps to Reproduce: 1. Download Workstation live Fedora 37 Rawhide 20220621.n.3 Base 2. Attempt to start the Graphical installer Anaconda (Install to hard drive.) 3. Actual results: Doesn't start even after 10 minutes Expected results: It will start as soon as it is clickede. Additional info:
Proposed as a Blocker and Freeze Exception for 37-beta by Fedora user ahmedalmeleh using the blocker tracking app because: Description of problem: Anaconda will not start upon click on install to hard drive or clicking on the taskbar icon. Version-Release number of selected component (if applicable): Fedora 37 Rawhide 20220621.n.3 Base How reproducible: Steps to Reproduce: 1. Download Workstation live Fedora 37 Rawhide 20220621.n.3 Base 2. Attempt to start the Graphical installer Anaconda (Install to hard drive.) 3. Actual results: Doesn't start even after 10 minutes Expected results: It will start as soon as it is clickede.
openQA is not reproducing this, the installer runs fine from the Workstation live in testing of 0621.n.3 and more recent composes. Can you try running 'liveinst' from a console and see if you get more output on the problem? Can you also look at `/tmp/anaconda.log` after attempting to launch the installer (if it's there) and see whether it says anything useful? Thanks!
It is still prevalent in recent coposes with manual testing. Here is the anaconda log in of the latest compose.
Created attachment 1899588 [details] Anaconda Log on Terminal
I set it top the basic graphics mode and it did load the installer on time. Very strange indeed.
(In reply to Ahmed Almeleh from comment #5) > I set it to the basic graphics mode and it did load the installer on time. > Very strange indeed.
We'd need you to attach the actual log file to the bug so we can see the whole thing, not just a screenshot of the first page :) But yeah, that's interesting, must be a graphical issue somehow, but it's unusual for things to work well enough to reach the desktop but not well enough to run anaconda. anaconda doesn't do much special with graphics.
Please, attach all files with installation logs. You can find them in the Live CD environment in the /tmp directory. Make sure that either the file syslog or journal.log is included. If neither file exists, please create the journal dump manually by running journalctl > journal.log and attach the file.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
Since this was proposed as a blocker and no sensitive info is present, I'm making this bug report public.
-5 in https://pagure.io/fedora-qa/blocker-review/issue/826 , marking rejected (both blocker and FE).
I think it have something with anaconda.pid, because the previous file “/var/run/anaconda.pid” exiting, when we run new anaconda we must clear this pid file
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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.