When Anaconda's crash reporting mechanism is invoked by a crash simulation using `rm -f /run/anaconda/backend_ready`, the user is asked for an API key and then is presented with a simplified dialog where they could describe what happened. This description, however is not passed to Bugzilla and the information gets lost. I am attaching a video that show what I typed in the description field and the created bug that is missing the info completely and only shows system info, see https://bugzilla.redhat.com/show_bug.cgi?id=2442592 Reproducible: Always Steps to Reproduce: 1. Start Anaconda WebUI 2. Crash it using the `rm -f /run/anaconda/backend_ready` command. 3. Fill in API key. 4. Fill in the description. 5. Report the problem. 6. See it in the newly opened bug. Actual Results: Anaconda passes incomplete information. Expected Results: Anaconda should pass all the fields completely. Additional Information: See attached video.
Proposed as a Blocker for 44-beta by Fedora user lruzicka using the blocker tracking app because: I am proposing this as a Beta blocker, because it violates one of the basic release criterion: https://fedoraproject.org/wiki/Basic_Release_Criteria#Failure_reporting
Upstream fix: https://github.com/rhinstaller/anaconda-webui/pull/1183
FEDORA-2026-3a377ea32c (anaconda-webui-66-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a377ea32c
FEDORA-2026-0d2fe998c1 (anaconda-webui-66-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-0d2fe998c1
FEDORA-2026-3a377ea32c has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3a377ea32c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3a377ea32c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
+3 for FE in https://pagure.io/fedora-qa/blocker-review/issue/2055 , marking accepted FE. Blocker vote still open.
FEDORA-2026-48bfc8a951 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-48bfc8a951` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-48bfc8a951 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Works for me in RC 1.2
Discussed on the Fedora Blocker Review Meeting on March, 2nd 2026 with the resolution. Accepted Beta Blocker See https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2026-03-02/f44-blocker-review.2026-03-02-17.00.log.txt
FEDORA-2026-f5c7f9e4c2 (anaconda-webui-67-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f5c7f9e4c2
FEDORA-2026-f5c7f9e4c2 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f5c7f9e4c2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f5c7f9e4c2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
66-2.fc44, which fixed this, was manually tagged stable: https://forge.fedoraproject.org/releng/tickets/issues/13243#issuecomment-574310 so this is now resolved. Once the freeze is lifted, 67-2.fc44 will be pushed stable and replace it.
FEDORA-2026-f5c7f9e4c2 (anaconda-webui-67-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.