Bug 608387

Summary: [abrt] crash in lmms-0.4.6-4.fc13: QMutex::lock: Process /usr/bin/lmms was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Chris Day <seinsinnes>
Component: lmmsAssignee: Thomas Moschny <thomas.moschny>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bugreporter1, thomas.moschny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:78129fd76e5a916748149ca138932cf49c39dc66
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-11 12:23:16 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 Chris Day 2010-06-27 06:36:29 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/lmms
component: lmms
crash_function: QMutex::lock
executable: /usr/bin/lmms
global_uuid: 78129fd76e5a916748149ca138932cf49c39dc66
kernel: 2.6.33.5-124.fc13.x86_64
package: lmms-0.4.6-4.fc13
rating: 4
reason: Process /usr/bin/lmms was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Chris Day 2010-06-27 06:36:32 UTC 
Created attachment 427180 [details]
File: backtrace
Comment 2 Thomas Moschny 2010-09-10 15:41:47 UTC 
lmms-0.4.8-1.fc13 has been pushed to the Fedora 13 testing repository.  If
problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update lmms'.  You can provide
feedback for this update here:
https://admin.fedoraproject.org/updates/lmms-0.4.8-1.fc13
Comment 3 Thomas Moschny 2010-10-11 12:23:16 UTC 
lmms-0.4.8-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.