Bug 620100 - [abrt] crash in lmms-0.4.6-2.fc12: Process /usr/bin/lmms was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in lmms-0.4.6-2.fc12: Process /usr/bin/lmms was killed by signal...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lmms
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e6cbe8df57a8c5172465f7c8277...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-31 21:41 UTC by Claudiomar Rodrigues
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:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (98.39 KB, text/plain)
2010-07-31 21:41 UTC, Claudiomar Rodrigues 		no flags Details
View All

Description Claudiomar Rodrigues 2010-07-31 21:41:18 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/lmms
component: lmms
executable: /usr/bin/lmms
global_uuid: e6cbe8df57a8c5172465f7c8277749deca297c46
kernel: 2.6.32.16-150.fc12.x86_64
package: lmms-0.4.6-2.fc12
rating: 4
reason: Process /usr/bin/lmms was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Claudiomar Rodrigues 2010-07-31 21:41:24 UTC 
Created attachment 435803 [details]
File: backtrace
Comment 2 Thomas Moschny 2010-09-10 15:40:32 UTC 
lmms-0.4.8-1.fc12 has been pushed to the Fedora 12 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.fc12
Comment 3 Thomas Moschny 2010-10-11 12:24:19 UTC 
lmms-0.4.8-1.fc12 has been pushed to the Fedora 12 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.