Bug 554027

Summary: [abrt] crash in lmms-0.4.5-2.fc12
Product: [Fedora] Fedora Reporter: Tyler Gillispie <mrteye>
Component: lmmsAssignee: Thomas Moschny <thomas.moschny>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: marbolangos, thomas.moschny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:f98c27665b4632b9a1a725ee8fd9ac5e21130c43
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-09 19:23:24 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 Tyler Gillispie 2010-01-10 03:28:13 UTC
abrt 1.0.3 detected a crash.

Comment
-----
. I am not sure what happened.
. Sound just stoped working and songs wouldn't paly.
. I could still move windows around.

Attached file: backtrace
cmdline: /usr/bin/lmms
component: lmms
executable: /usr/bin/lmms
kernel: 2.6.31.9-174.fc12.x86_64
package: lmms-0.4.5-2.fc12
rating: 3
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Tyler Gillispie 2010-01-10 03:28:15 UTC
Created attachment 382748 [details]
File: backtrace

Comment 2 Thomas Moschny 2010-01-18 12:13:03 UTC
Sounds like a problem with  the sound backend. Is the problem specific to one backend?

Also, please try to reproduce the crash using the latest version of the package
http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0664

Comment 3 Thomas Moschny 2010-02-08 08:30:17 UTC
Can you please try to reproduce that using lmms 0.4.6 ?

Comment 4 Fabien Archambault 2010-02-08 19:47:12 UTC
It seems that in my computer i cannot reproduce the crash with the 0.4.6 version.

Comment 5 Thomas Moschny 2010-02-09 19:23:24 UTC
(In reply to comment #4)
> It seems that in my computer i cannot reproduce the crash with the 0.4.6
> version.    

So, this is a good message ;)

I'm going to close the bug for now, feel free to reopen resp. make a new ticket when the crash happens again.