Bug 2317767 - anaconda error dialog flashes and disappears when the error occurs early during startup
Summary: anaconda error dialog flashes and disappears when the error occurs early duri...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 41
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-10 08:29 UTC by Kamil Páral
Modified: 2025-12-16 17:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 17:15:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2316058 0 unspecified CLOSED anaconda fails to start when a device requires fsck 2024-10-10 08:30:38 UTC

Internal Links: 2316058

Description Kamil Páral 2024-10-10 08:29:13 UTC
Description of problem:
In bug 2316058 we've demonstrated a problem during which anaconda crashes in early initialization when blivet examines available disks. When this happened, the error dialog (in which the traceback can be seen and reported to Bugzilla) just briefly flashes on the screen and immediately disappears. This is a problem, because it doesn't allow the user to report the issue.

Please make sure that the error dialog is always usable, even when the error happens early (before the first screen is shown).


Version-Release number of selected component (if applicable):
anaconda-41.31-1.fc41.x86_64

How reproducible:
the original problem was fixed, and so in order to reproduce it, the patch from bug 2316058 needs to be reverted, or some other problem needs to be introduced in anaconda code to simulate this situation (i.e. blivet returning some error, even when disks are actually fine).

Additional info:
Some details about why the error dialog disappears might be present in logs in bug 2316058.

Comment 1 Katerina Koukiou 2024-10-15 12:45:03 UTC
An issue with the same root cause has been resolved in the Web UI (see https://bugzilla.redhat.com/show_bug.cgi?id=2308279). Given that the underlying blivet bug has also been addressed, we will defer handling this for now, at least until the future of the Web UI is clarified.

Comment 2 Adam Williamson 2025-12-02 01:21:10 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
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 '41'.

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 41 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.

Comment 3 Samyak Jain (RedHat) 2025-12-16 17:15:29 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 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.


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