Bug 603619

Summary: [abrt] crash in lxmusic-0.4.2-1.fc13: raise: Process /usr/bin/lxmusic was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: William M. Quarles <walrus>
Component: lxmusicAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: https://sourceforge.net/tracker/?func=detail&aid=3030573&group_id=180858&atid=894869
Whiteboard: abrt_hash:46e4b0788e9e5ead6d7fbc554999df35b30ca55a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 14:29:42 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 William M. Quarles 2010-06-14 07:48:40 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: lxmusic
component: lxmusic
crash_function: raise
executable: /usr/bin/lxmusic
global_uuid: 46e4b0788e9e5ead6d7fbc554999df35b30ca55a
kernel: 2.6.33.5-112.fc13.i686.PAE
package: lxmusic-0.4.2-1.fc13
rating: 4
reason: Process /usr/bin/lxmusic was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Open lxmusic.
2. Lock for a file but don't open one.
3. close lxmusic
Comment 1 William M. Quarles 2010-06-14 07:48:42 UTC 
Created attachment 423752 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-16 14:29:42 UTC 
Thanks for your bug report. I forwarded it upstream as https://sourceforge.net/tracker/?func=detail&aid=3030573&group_id=180858&atid=894869

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.

I'm now closing the bug UPSTREAM because this is where further investigation should take place.