Bug 909596

Summary: Unable to report bug in /usr/libexec/mission-control-5
Product: [Fedora] Fedora Reporter: Scott Schmit <i.grok>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: abrt-devel-list, dvlasenk, iprikryl, jfilak, jmoskovc, keramidasceid, mmilata, mtoman, rh-bugzilla, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: abrt-2.1.4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-06 07:58:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Dump Directory Archive for Bug 909596, 20130219 rh-bugzilla: review+

Description Scott Schmit 2013-02-09 18:24:31 UTC 
Description of problem:
I've got several segfaults in /usr/libexec/mission-control-5 that I can't report via ABRT because I get this error:

--- Running report_uReport ---
Generating backtrace
Server side error: '"Validation failed: error validating 'installed_package': missing mandatory element 'release'"'
(exited with 1)

I don't know if this is a bug in ABRT or not, but all packages have releases, so I think ABRT is confused and trying to look up something that's not a package?

Version-Release number of selected component (if applicable):
abrt-addon-ccpp-2.0.20-1.fc18.x86_64
abrt-2.0.20-1.fc18.x86_64
abrt-addon-python-2.0.20-1.fc18.x86_64
abrt-addon-kerneloops-2.0.20-1.fc18.x86_64
abrt-libs-2.0.20-1.fc18.x86_64
abrt-addon-vmcore-2.0.20-1.fc18.x86_64
abrt-retrace-client-2.0.20-1.fc18.x86_64
abrt-desktop-2.0.20-1.fc18.x86_64
abrt-dbus-2.0.20-1.fc18.x86_64
abrt-gui-2.0.20-1.fc18.x86_64
abrt-plugin-bodhi-2.0.20-1.fc18.x86_64
abrt-addon-xorg-2.0.20-1.fc18.x86_64

How reproducible:
100% (on my machine)

Steps to Reproduce:
1. Get a segfault in /usr/libexec/mission-control-5
2. Open ABRT, double-click the line with the above in it
3. "Process /usr/libexec/mission-control-5 was killed by signal 11 (SIGSEGV) - abrt" window opens
4. After talking to the server, it says "Processing Failed" and gives me the option to show log or close.
5. If I show log, I get the above
  
Actual results:
I have segfaults in my applications, and I can't report them, just delete them

Expected results:
I should be able to report the segfault and hopefully someone will fix it. :)

Additional info:
"rpm -qf /usr/libexec/mission-control-5" yields "telepathy-mission-control-5.14.0-2.fc18.x86_64" which has a release of "2.fc18", per RPM.
Comment 1 Jakub Filak 2013-02-09 23:02:14 UTC 
Thank you for taking the time to report this bug. Unfortunately, without the dump directory it is almost impossible to determine what caused this error. If you have time, please provide the dump directory so we can diagnose the problem. The dump directory should be located either in /var/spool/abrt directory or in ~/.cache/abrt/spool directory. Thank you.
Comment 2 Richy Hareter 2013-02-19 19:48:04 UTC 
Created attachment 699614 [details]
Dump Directory Archive for Bug 909596, 20130219

I also have the same bug on my machine, so I created an archive with the dump directory. Hope it helps.

richy
Comment 3 Jakub Filak 2013-08-06 07:58:27 UTC 
Thank you for the bug report. The message says that problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out. If you have time and want to help the developers in their effort to sort out this problem, please contact them directly.

These kind of problems are detected automatically since abrt-2.1.4
Upstream commit 575323612142b12c13a165cb41c792592527c5d4