Description of problem:
With the 19 Alpha TC1 DVD (i386 or x86_64), https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla fails. I use the fake exception handling trigger. When the window "An unknown error has occurred." appears, I click on "Report Bug", then "Report a bug to Fedora maintainers", then "Configure Bugzilla", then fill in the info, then "OK". The "How did this problem happen (step-by-step)?" screen has nothing except a Close button, so there appears to be no way to report a bug, and indeed no bug appears in Bugzilla when I hit it.
Version-Release number of selected component (if applicable):
19.12 (from 19 Alpha TC1)
Proposing as Alpha Blocker based on https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria#Failure_reporting : "The installer must be able to report failures to Bugzilla, with appropriate information included."
I also found it and i had to manually report those bugs.
Discussed at 2013-03-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-blocker-review-3.2013-03-27-16.01.log.txt . Accepted as a blocker per criterion cited in comment #1.
libreport-2.1.3-2.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreport-2.1.3-2.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Any way to test this with non-Live install media?
Reproduced with TC5, verified fixed with RC1 (viz. https://bugzilla.redhat.com/show_bug.cgi?id=949781 ). Setting VERIFIED.
Yes, I managed to file a bug with a backtrace from RC2.
I filed a bug through RC2 also
libreport-2.1.3-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.