Red Hat Bugzilla – Bug 561704
[abrt] crash in muse-1:1.0-1.fc12
Last modified: 2010-12-03 18:20:58 EST
abrt 1.0.4 detected a crash.
Attached file: backtrace
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Created attachment 388711 [details]
Thanks for the report. Could you tell us how to reproduce the crash?
I remember the crash during the exit of the application. After your message I tried the application again and again , but it denied tenaciously to repeat the desired "crash moment"...
....well, Jack is running (and it's ok) and I open the Muse application. Then I simply add a midi track and I wanted to continue searching the above problem but ... my wife told to me that the dinner was ready and I had to stop immediately my work in front of the computer , if I loved my life ....!! So, I closed the application without saving anything and to my surprise the ABRT mentioned the crash !! That's all. I must turn off the PC now , because the "nuclear reactor" will explode in my small dining room..... Thanks a lot for your interest.
I also noticed that the application was always crashed when I tried to input midi signals from the "midi through" port. I think that the procedure I followed was correct because Rosegarden did it successfully.
The midi input section of the code saw extensive changes lately. This might have been fixed upstream. Could you try the latest build 1.0.1 from
I submitted this one to updates-testing yesterday.
If it is still broken for you, we might as well contact upstream.
Forgive me because Iam new in Linux and I don't know how to build applications. Generally I avoid the experiments because I am not in position to face side effects. Can I install this new muse somehow with the package manager if I expand the software sources and mark the Fedora 12 Test-updates repo ?
No problem. These are official builds that will be in the updates-testing repo in a couple days (or possibly later today). You don't need to rebuild them.
You can either download the appropriate RPM package for your architecture and install it. For example, you would update via (as root)
# rpm -Uvh muse-1.0.1-1.fc12.x86_64.rpm
for the x86_64 architecture.
Or if this is complicated, wait a little, the packages will be in the updates-testing repo soon. Then you can install it with your package manager.
The 1.0.1 version is in testing repository now. It can be installed via
# yum --enablerepo updates-testing update muse
or with your favorite package management software.
Well , I did it and I have already 2 crashes. The first one was done because I did not run jack before I run muse. I believe that if someone wants to work only with midi he doesn't need jack. The second crash was done because the muse application "does not want" to receive midi data by the midi through port. You know I use other applications in parallel with muse. The midi through port can send midi data to other applications normally, but I can't discover a way to pass midi data to muse reversely. Somehow I did it with rosegarden. Generally, I can see the same muse as before. I can see the midi channels 1-16 (one by one) but I can't see the indication "Any channel" for multichannel midi data recording. I can't understand the per cent indication next to tempo box. The tempo can be a fixed value or an altered one. I need a tempo track or something like that to define an altered tempo for any midi song. You can see it in Cubase (windows application). Anyway , I am new in Linux and I have not enough experience on Linux midi-sequencer applications, so forgive me if I say something wrong here. I am only an amateur music composer (6-7 years) and I mainly use midi keyboards, midi sequencers and other useful midi tools.
*** Bug 563933 has been marked as a duplicate of this bug. ***
*** Bug 564256 has been marked as a duplicate of this bug. ***
*** Bug 567025 has been marked as a duplicate of this bug. ***
*** Bug 570345 has been marked as a duplicate of this bug. ***
*** Bug 573422 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
*** Bug 595144 has been marked as a duplicate of this bug. ***
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.