This is an F18 system, which is getting the whole new abrt/gnome-abrt/libreport clump as updates from updates-testing. With libreport and abrt 2.1.3 and gnome-abrt 0.2.11, many of my existing crashes show up as "?? crashed" in gnome-abrt , and clicking the Report button does nothing. Since I started writing this report, some more kernel oopses have happened, and even some of them are buggy, so it's not just old reports, apparently. I will attach some of the problem directories.
jmoskovc suggests that (one of) the problem(s) here is that gnome-abrt tries to populate the field that's showing up as ?? based on the .desktop file, which obviously isn't going to work when there isn't one. Lots and lots of stuff without .desktop files crashes. I'll attach some samples.
Created attachment 742914 [details] This problem shows as "?? crashed", left hand side shows "?? (newline) Kerneloops" and the date
Created attachment 742917 [details] this problem shows as "?? crashed", no details in right hand pane, no "Kerneloops" in left hand list, cannot be reported
Created attachment 742919 [details] This problem shows as "?? crashed", left hand list shows just "??" and date and count, right hand side shows "Name ??" "Version: GConf2-3.2.5-3.fc17", cannot be reported
(In reply to comment #2) This problem was detected while computer was shutting down (abrt-2.1.4 should be able to recognize these problems and provide an appropriate explanation).
Fixed in upstream git: commit 8c1df4e7c106609472dee0b08f7d1a3263d890fa Author: Jakub Filak <jfilak> Date: Fri May 3 09:47:54 2013 +0200 Use 'N/A' instead of ?? Closes rhbz#958974 (comment #2) Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Jiri Moskovcak <jmoskovc> commit 8dd5953d862a6b638d546fdd955b64307a47feb8 Author: Jakub Filak <jfilak> Date: Fri May 3 09:47:53 2013 +0200 Use package name is neither component nor executable items are available Related to rhbz#958974 (comment #3, comment #4) Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Jiri Moskovcak <jmoskovc>
gnome-abrt-0.2.12-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gnome-abrt-0.2.12-1.fc19
Package gnome-abrt-0.2.12-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 gnome-abrt-0.2.12-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7321/gnome-abrt-0.2.12-1.fc19 then log in and leave karma (feedback).
Please submit it / edit the updates for F17 and F18 too - I reported this on 18.
Package gnome-abrt-0.2.12-3.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 gnome-abrt-0.2.12-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7321/gnome-abrt-0.2.12-3.fc19 then log in and leave karma (feedback).
gnome-abrt-0.2.12-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.