Bug 613179

Summary: [abrt] crash in xarchiver-0.5.2-5.fc12: do_sigtimedwait: Process was terminated by signal 6 (Aborted)
Product: [Fedora] Fedora Reporter: Svante Victorsson <svante.victorsson>
Component: xarchiverAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: https://sourceforge.net/tracker/?func=detail&aid=3030710&group_id=140153&atid=745600
Whiteboard: abrt_hash:82335b5b259cd5d08a7e7cb199f08a97311fef15
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 18:58:51 UTC Type: ---
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
File: backtrace none

Description Svante Victorsson 2010-07-09 21:28:07 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: xarchiver /tmp/kernelbase147.rar
component: xarchiver
crash_function: do_sigtimedwait
executable: /usr/bin/xarchiver
global_uuid: 82335b5b259cd5d08a7e7cb199f08a97311fef15
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: xarchiver-0.5.2-5.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)
Comment 1 Svante Victorsson 2010-07-09 21:28:10 UTC 
Created attachment 430766 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-16 18:58:51 UTC 
Thanks for reporting this bug. I have forwarded the report to the upstream developers as https://sourceforge.net/tracker/?func=detail&aid=3030710&group_id=140153&atid=745600

I'm now closing the bug UPSTREAM because this is where further investigation should take place. Feel free to add yourself to the upstream bug report in order to follow any changes. Even if you don't, will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you.