Description of problem: After updating anaconda and pykickstart, upon an anaconda crash, clicking the Report Bug button causes the dialog to briefly vanish but then it reappears. There is no way to automatically report anaconda bugs for an updated anaconda. Version-Release number of selected component (if applicable): Fedora-Live-Desktop-x86_64-19-Alpha-1.iso libreport-2.1.3-2 The following files are updated when executing 'yum update anaconda pykickstart': pykickstart-1.99.26-1 -> 1.99.28-1 anaconda-widgets-19.20-1 -> 19.22-1 anaconda-19.20-1 -> 19.22-1 python-meh-0.22-1 -> 0.23-1 How reproducible: Always. Steps to Reproduce: 1. Live image boot, Vbox VM, 80GB image. 2. Terminal, 'yum update anaconda pykickstart' 3. Launch the installer. 4. At Installation Options: selection review/modify partitions; and change partition scheme to btrfs. 5. Manual partitioning, click +, mount point /, desired capacity 82gb. Actual results: Anaconda crashes, a libreport dialog appears, and the Report Button doesn't work. Clicking on the button causes the dialog to briefly disappear, but then it reappears. Expected results: For the button to lead to a path allowing automatically filing of the captured crash data. Regression: Crash does not occur if anaconda and pykickstart are not updated in step 2.
Vratislav, are there any changes in the new version of the mentioned packages which might be interfering with libreport?
(In reply to comment #1) > Vratislav, are there any changes in the new version of the mentioned > packages which might be interfering with libreport? I think the dialog mentioned in the description is the python-meh's dialog and it looks like a problem with libreport invocation. I'll try to find out what's happening, it may be caused by the changes introduced due to bug #929181, but that's only a guess.
(In reply to comment #2) > (In reply to comment #1) > > Vratislav, are there any changes in the new version of the mentioned > > packages which might be interfering with libreport? > I think the dialog mentioned in the description is the python-meh's dialog > and it looks like a problem with libreport invocation. I'll try to find out > what's happening, it may be caused by the changes introduced due to bug > #929181, but that's only a guess. My guess was right. Reassigning to python-meh.
Patch posted to anaconda-patches mailing list.
python-meh-0.24-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-meh-0.24-1.fc19
Package python-meh-0.24-1.fc19: * 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 python-meh-0.24-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7275/python-meh-0.24-1.fc19 then log in and leave karma (feedback).
Nominating as a Beta blocker, under 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." (Beta requirements include all Alpha requirements).
Discussed at 2013-05-06 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-06/f19beta-blocker-review-3.2013-05-06-16.02.log.txt . Accepted as a blocker per criterion cited in comment #7.
This fix is in TC3; can anyone confirm it yet? (I haven't hit a traceback with TC3 yet myself).
Ah. From Bodhi: snoopylane - 2013-05-05 01:02:36 anaconda crash with Fedora-19-Beta-TC3-x86_64-netinst.iso and I was able to submit a bugreport (959710) setting verified.
The update went stable, closing.