Red Hat Bugzilla – Bug 849070
Anaconda's bug reporter doesn't work
Last modified: 2012-09-06 12:21:52 EDT
Description of problem:
Window that should serve for bug reporting doesn't work. Window is shown correctly when error appears, but I can't click on anything. So I'm unable to report bug.
Version-Release number of selected component (if applicable):
Alpha TC3 DVD.iso
Steps to Reproduce:
1. Try to find some error in anaconda (in TC3 - click on configure button in Network settings spoke)
Window for reporting appears, but I can't click on anything.
The window should work correctly, I should be able to report a bug via this.
I propose this as alpha blocker as it violates this criterion:
"The installer must be able to report failures to Bugzilla and local disk, with appropriate information included"
(In reply to comment #0)
> Description of problem:
> Window that should serve for bug reporting doesn't work. Window is shown
> correctly when error appears, but I can't click on anything. So I'm unable
> to report bug.
This is a know issue and it happens only if the exception window appears above a spoke (hubs and standalone-spokes are ok). Patch for this issue is waiting for a review and pushing.
Discussed at 2012-08-20 QA meeting, acting as a blocker review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2012-08-20/fedora-qa.2012-08-20-15.00.html . Accepted as a blocker per criterion "The installer must be able to report failures to Bugzilla and local disk, with appropriate information included".
Patch for this issue has been pushed to anaconda git repository (e5fd667e1402a0355ef2663571c41454f25c3caf)
anaconda-18.6.1-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.6.1-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Using TC4, i just had a traceback and was able to report a issue using anaconda reporting ( 853376 ), so this is likely fixed.
Using the TC4 x86_64 netinstall, I forced a crash with the following updates.img:
Libreport starts up and attempts to file a new bug, so it appears as if this bug has been fixed. Moving to VERIFIED.
18.6.5-1 was pushed stable, so closing.