Bug 573422 - [abrt] crash in muse-1:1.0.1-1.fc12: Process /usr/bin/muse was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in muse-1:1.0.1-1.fc12: Process /usr/bin/muse was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 561704
Alias: None
Product: Fedora
Classification: Fedora
Component: muse
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Orcan Ogetbil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:07bc092258148053837110795f8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-14 19:05 UTC by Fanis Attard
Modified: 2010-03-15 04:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-15 01:10:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.61 KB, text/plain)
2010-03-14 19:05 UTC, Fanis Attard
no flags Details

Description Fanis Attard 2010-03-14 19:05:28 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: muse
component: muse
executable: /usr/bin/muse
kernel: 2.6.32.9-70.fc12.x86_64
package: muse-1:1.0.1-1.fc12
rating: 4
reason: Process /usr/bin/muse was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Fanis Attard 2010-03-14 19:05:32 UTC
Created attachment 400027 [details]
File: backtrace

Comment 2 Fanis Attard 2010-03-14 19:32:21 UTC
I had the previous version of Rosegarden. After this update , I could see Rosegarden as an option in the menu, but I could not start the application clicking on it. I also want to report that my previous rosegarden link button on the desktop disappeared after this update ! I noticed that I could start the application using the terminal , so I used the launcher properties and I changed the command "rosegarden  -caption "%c" %i %m" with the very simpler "rosegarden". So , to my surprise, it seems ok now , I can start the application normally by the menu.

The above crash is reported by the ABRT every time and immediately after I close the rosegarden application.

Comment 3 Fanis Attard 2010-03-14 19:38:12 UTC
I noticed on this page that as component it seems the muse application !! It is not a muse crash , but a rosegarden crash. I really don't understand what is happening here.

Comment 4 Orcan Ogetbil 2010-03-15 01:10:03 UTC
I have no idea what in going on here. 

You crashed muse by just using rosegarden?

Can you close all muse instances before starting rosegarden and report the bug with the rosegarden crash? Thanks!

By the way, I still have rosegarden in my menu. What DE are you using? Do you have the "multimedia-menus" package installed (you don't have to install this but it just makes it easier to locate your audio applications in the menu)? 

Also I noticed that you have pulseaudio installed. pulseaudio is known to cause problems with audio production applications which are geared for low latency. I advise you to remove pulseaudio if you are doing audio productional work, unless you know what you are doing. I personally don't use pulseaudio. It caused very many problems to me in the past.

(The muse backtrace that is attached is the same crash as in bug 561704. The developers are informed and they are working on it. There is no need to re-report it.)

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

Comment 5 Fanis Attard 2010-03-15 04:33:20 UTC
Thanks a lot Orcan. I will remove pulseaudio. The above crash I mentioned caused by rosegarden. Please remove it , if you can.


Note You need to log in before you can comment on or make changes to this bug.