Description of problem:
When proceeding with this test case , I tried to kill Anaconda running in text mode to use the automatic reporting to Bugzilla. Anaconda crashed in with a traceback. In graphical mode, the error was correctly reported.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start Anaconda in text mode (using inst.text on prompt)
2. Kill it according to the test case using
kill -USR1 `cat /var/run/anaconda.pid`
3. Chose options to report the bug.
3. Save the report file using :wq
4. Wait for Anaconda to crash.
Anaconda crashes with the traceback, see screenshot.
Anaconda should be able to report the bug correctly to Bugzilla.
Created attachment 1408897 [details]
Created attachment 1408898 [details]
Dnf librepo log
Created attachment 1408899 [details]
Created attachment 1408900 [details]
Created attachment 1408901 [details]
Created attachment 1408902 [details]
Proposed as a Blocker for 28-beta by Fedora user lruzicka using the blocker tracking app because:
This bug affects the Basic Release Criteria. The installer must be able to report failures to Bugzilla, with appropriate information included.
Discussed at 2018-03-19 Fedora 28 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-03-19/f28-blocker-review.2018-03-19-16.02.html . As the report is actually failed, but anaconda crashes before displaying the URL, we decided this wasn't a serious enough violation to constitute a Beta blocker, but it is serious enough to constitute a Final blocker. We also accepted it as a freeze exception issue for Beta, as obviously it'd be good to fix this if possible.
Siiiiigh. Serves me right for using the same scratch text file for a) blocker secretary work and b) air conditioner maintenance. :P
Based on my discover the proper fix should be done in Simpleline.
Jiri - any news on this? It's blocking Final, and we're coming up on Final now. Freeze is in a couple of weeks. Thanks!
Work in progress.
Sorry I forgot to move it to post.
This was actually included in https://bodhi.fedoraproject.org/updates/FEDORA-2018-205aabf6cb , but it wasn't tagged. We just need to confirm whether the fix worked, then we can close this.
On 20180415.n.0 compose, I can confirm that it works and the bug is created correctly.
However take into account this bug 1541868
I also tested this and it works and reports the bug correctly. However, the bug Alessio speaks about in Comment 14 is still relevant. The fuzz is still produced.
Thanks for the confirmation, Alessio, Lukas. I think the spam would be an FE issue not a blocker one, unfortunately doesn't look like anyone has picked it up to work on yet :( I'll poke the libreport folks and see if anything drops loose.
Since reporting does actually work now, we can close this one.