Description of problem: if I select a bug that hasn't been reported yet in ABRT's GUI and click the 'Report' button it fails. http://www.zimagez.com/zimage/screenshot-11122012-034301pm.php I can report the bug if I go to 'Problem'>'Open problem data' 'abrt-cli report <bug>' also works properly. Version-Release number of selected component (if applicable): $ yum list *abrt* Loaded plugins: auto-update-debuginfo, downloadonly, presto, remove-with-leaves Installed Packages abrt.i686 2.0.18-1.fc18 @updates-testing abrt-addon-ccpp.i686 2.0.18-1.fc18 @updates-testing abrt-addon-kerneloops.i686 2.0.18-1.fc18 @updates-testing abrt-addon-python.i686 2.0.18-1.fc18 @updates-testing abrt-addon-xorg.i686 2.0.18-1.fc18 @updates-testing abrt-dbus.i686 2.0.18-1.fc18 @updates-testing abrt-gui.i686 2.0.18-1.fc18 @updates-testing abrt-libs.i686 2.0.18-1.fc18 @updates-testing abrt-plugin-bodhi.i686 2.0.18-1.fc18 @updates-testing abrt-retrace-client.i686 2.0.18-1.fc18 @updates-testing abrt-tui.i686 2.0.18-1.fc18 @updates-testing Available Packages abrt-addon-vmcore.i686 2.0.18-1.fc18 updates-testing abrt-cli.i686 2.0.18-1.fc18 updates-testing abrt-desktop.i686 2.0.18-1.fc18 updates-testing abrt-devel.i686 2.0.18-1.fc18 updates-testing gnome-abrt.i686 0.2.3-1.fc18 fedora rubygem-abrt.noarch 0.0.3-1.fc18 fedora rubygem-abrt-doc.noarch 0.0.3-1.fc18 fedora How reproducible: always Steps to Reproduce: 1. Open 'Automatic Bug reporting Tool' 2. Select a still not reported bug 3. Click 'Report' Actual results: fails with ureport related error Expected results: should report the bug Additional info:
Could you please provide more verbose log output? Run abrt-gui in verbose mode and report your bug again. $ abrt-gui -vvv
Created attachment 646766 [details] Verbose terminal output of a failed report. Here's the terminal output. When running without -vvv it would give the same error as the first post.
Do you remember when was the crash detected (e.g. after login to desktop session)?
abrt-applet reports right after any crash. Sometimes I notice that if I leave a crash un-reported and also don't click on 'Ignore' in the notification pop-up then it will alert again on next login (but I haven't checked this behaviour if it's exactly like that). In the case on comment #2, since you asked for a log output, I just ran it and there was one crash not-reported so I left it selected and clicked on 'Report'.
(In reply to comment #4) > abrt-applet reports right after any crash. We've recently discovered an ugly race which has the similar symptoms like in your case. The race comes when system is rebooting or halting. (It could explain my question.) > Sometimes I notice that if I leave a crash un-reported and also don't click > on 'Ignore' in the notification pop-up then it will alert again on next > login (but I haven't checked this behaviour if it's exactly like that). I can confirm that it is exactly like that. But any further click either on 'Report' or on 'Ignore' button will add all un-reported and un-ignored crashes to the seen crashes list and the crashes won't be shown on next login. > > In the case on comment #2, since you asked for a log output, I just ran it > and there was one crash not-reported so I left it selected and clicked on > 'Report'. Good work! Now we know that post-create event failed. We know it because of missing core_backtrace field. I expect that a log from the event run has been lost, but we can run post-create event again. Please, run the following commands and provide a log output: # I hope that you have not yet deleted the crash. cd /home/first/.cache/abrt/spool/ccpp-2012-11-15-16:31:09-1433 /usr/libexec/abrt-handle-event -vvv -e post-create .
Created attachment 648870 [details] Requested output log.
If you mean similar symptoms to the bug we're using to debug abrt, it's a file-roller crash (the first report was a Thunar issue) but it was something occasional when opening several apps at the same time. My system is old and while there's no sign of bad RAM or HD I suspect that since most apps are developed nowadays in powerful machines I notice that they can give weird crashes due to my machine being slow and single-core. That's why this bug was destined to be simply deleted if it wasn't serving to debug abrt. I'm not a programmer but this is my experience as user. If your mention of the ugly race isn't related to the bug report we're using then pardon me, I may have just misunderstood it.
(In reply to comment #6) > Created attachment 648870 [details] > Requested output log. Argh, I'm sorry! abrt-handle-event was bad choice. It produces very poor log output. Please, run the following commands and provide a log output again: cd /home/first/.cache/abrt/spool/ccpp-2012-11-15-16:31:09-1433 report-cli -vvv -e post-create .
Created attachment 649161 [details] report-cli output log.
The log output looks OK to me. Is it still impossible to report the crash? If so, please, attach /home/first/.cache/abrt/spool/ccpp-2012-11-15-16:31:09-1433 directory.
Created attachment 649306 [details] compressed folder Clicking on 'Report' fails with that uReport error (screenshot in first post). IDK if it's related, but I use Xfce and I don't have GNOME keyring installed. Note that as I said, it's only the 'Report' button that doesn't work. abrt-cli and reporting first by opening problem data work fine.
Just posting in case it's related. When I go to 'Help>Report a problem with ABRT', write something and click on 'Send', I get this error: http://ompldr.org/vZ2VvYQ
Good news. It's working today. 2.0.19-2.fc18 But libreport/ureport are 2.0.19-3.fc18 already. I'm even reporting a report-gtk crash soon ;-)
Is it working even with the crash from comment #11?
Unfortunately I deleted it. It worked with https://bugzilla.redhat.com/show_bug.cgi?id=884778 and https://bugzilla.redhat.com/show_bug.cgi?id=884791
Ok, had another crash and it failed with --- Running report_uReport --- (exited with 1)
(In reply to comment #12) > Just posting in case it's related. > When I go to 'Help>Report a problem with ABRT', write something and click on > 'Send', I get this error: > http://ompldr.org/vZ2VvYQ I've fixed the problem with abrt-gui>Help commit b61064ce04d3124bc99c17fec3f3f9123574a7c2 Author: Jakub Filak <jfilak> Date: Fri Dec 7 18:36:22 2012 +0100 rework abrt-gui>Help>'Report problem with ABRT' However, it doesn't mean that this bugzilla is fixed ;) I'm still working on it.
Fixed on client-side but needs to be fixed on server-side as well. commit 52426ddb8f1b28b6ec5e0e12944f9c51acebbded Author: Jakub Filak <jfilak> Date: Mon Dec 10 17:51:34 2012 +0100 core bactrace: mark empty buildids as unknown
This has been fixed on the server side some time ago.