Report bug button (abrt) not usable
rugk opened this issue · comments
I had issue storaged-project/blivet#919, so I clicked the "Report bug" button.
Abrt opens and I can report the bug there.
However – that is broken because of usability reasons.
Bug reporting bug
Also, BTW, the "Report a bug" button is useless/broken, as it opens the gnome-abrt GUI when cloicked and I can report a bug there, but clicking that button does nothing…
… oh wait… it seems I have to wait for several seconds and it then has collected data.
Buuut…, it seems to exit/crash soon after that and thus abrt cannot find the files anymore at some step. The slower I am when clicking through that, the likelier the dir is already removed:
So effectively it removes the dir faster than I can use it for reporting the bug.
I moved the issues to blivet-gui, because this is "GUI only" feature, but I also think this is a problem in ABRT, not blivet-gui. I wasn't able to reproduce this behaviour, but I'll try harder and possibly report a bug against ABRT.
The idea behind this "feature" is quite simple and everything is done by ABRT itself -- it should automatically detect the crash and create the report (including blivet/blivet-gui specific logs). The only thing the "Report a bug" button does is raising the exception and starting ABRT. I tested this on Fedora 32 (abrt 2.14.1) and the report (and the /var/spool/abrt/<report> directory) is not deleted even after few hours. If you run abrt manually you should still see all reports from previous crashes.
I'll try to look into ABRT API, maybe blivet-gui could be smarter about this and try to wait for ABRT to collect the data before opening it, right now it's just a very simple "run ABRT and let it handle the crash" button.