Bug 567025

Summary: [abrt] crash in muse-1:1.0-1.fc12
Product: [Fedora] Fedora Reporter: Mark Cochran <remarkable485>
Component: museAssignee: Orcan Ogetbil <oget.fedora>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: nando, oget.fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:1e1205be5ab52f2470a427525f2eb27f1811d6ce
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-09 06:48:09 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 Mark Cochran 2010-02-21 06:27:15 UTC 
abrt 1.0.6 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: muse
comment: muse crashes with segmentation fault
component: muse
executable: /usr/bin/muse
kernel: 2.6.31.12-1.rt20.1.fc12.ccrma.x86_64.rt
package: muse-1:1.0-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. install ccrma rpm's and rt kernel, and muse
2. boot to rt kernel	
3. run muse binary
Comment 1 Mark Cochran 2010-02-21 06:27:17 UTC 
Created attachment 395320 [details]
File: backtrace
Comment 2 Orcan Ogetbil 2010-02-21 06:51:35 UTC 
This may be an rt kernel issue (if it doesn't happen on Fedora's kernel)

Could you post this on PlanetCCRMA's mailing list? You can just give a link to this bug.

By the way, there is a new version muse-1.0.1 in updates-testing. You might want to check it out.
Comment 3 Orcan Ogetbil 2010-03-09 06:48:09 UTC 
I realized that this is the same crash on start that Fanis reported a while ago. A workaround is given in
https://bugzilla.redhat.com/show_bug.cgi?id=570345#c12

*** This bug has been marked as a duplicate of bug 561704 ***