Bug 622355 - [abrt] crash in lmms-0.4.6-4.fc13: QMutex::lock: Process /usr/bin/lmms was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lmms-0.4.6-4.fc13: QMutex::lock: Process /usr/bin/lmms was ki...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lmms
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4a49d0a0103b9b8023b3fbd4b21...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-09 03:49 UTC by Jesse
Modified: 2010-10-11 12:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-11 12:24:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (51.43 KB, text/plain)
2010-08-09 03:49 UTC, Jesse 		no flags Details
View All

Description Jesse 2010-08-09 03:49:26 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: 4a49d0a0103b9b8023b3fbd4b215e028fa2a409b
kernel: 2.6.33.6-147.2.4.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 Jesse 2010-08-09 03:49:28 UTC 
Created attachment 437515 [details]
File: backtrace
Comment 2 Thomas Moschny 2010-09-10 15:42:33 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:24:38 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.
Note You need to log in before you can comment on or make changes to this bug.