Description of problem: I have installed Jack during the day and few minutes ago, I installed Rosegarden. Then I record some seconds of playing. When I try to listen what I have just recorded with roseGarden, it crash. I try to stop jack with qjackctl interface but it crash aswell and propose this report. (Sorry for my english) Version-Release number of selected component: rosegarden4-12.04-3.fc17 Additional info: backtrace_rating: 4 cmdline: rosegarden crash_function: operator-- executable: /usr/bin/rosegarden kernel: 3.7.9-104.fc17.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 operator-- at /usr/include/c++/4.7.0/bits/stl_tree.h:284 #1 freeChannelInterval at src/base/AllocateChannels.cpp:155 #2 Rosegarden::FreeChannels::freeChannelInterval at src/base/AllocateChannels.cpp:140 #3 Rosegarden::AllocateChannels::reallocateToFit at src/base/AllocateChannels.cpp:387 #4 Rosegarden::ChannelManager::reallocate at src/gui/seqmanager/ChannelManager.cpp:403 #5 Rosegarden::ChannelManager::setInstrument at src/gui/seqmanager/ChannelManager.cpp:460 #6 Rosegarden::InternalSegmentMapper::doInsert at src/gui/seqmanager/InternalSegmentMapper.cpp:488 #7 Rosegarden::MappedEventBuffer::iterator::doInsert at src/gui/seqmanager/MappedEventBuffer.cpp:291 #8 Rosegarden::MappedBufMetaIterator::fillNoncompeting at src/sound/MappedBufMetaIterator.cpp:366 #9 Rosegarden::MappedBufMetaIterator::fillCompositionWithEventsUntil at src/sound/MappedBufMetaIterator.cpp:232
Created attachment 707603 [details] File: backtrace
Created attachment 707604 [details] File: build_ids
Created attachment 707605 [details] File: cgroup
Created attachment 707606 [details] File: core_backtrace
Created attachment 707607 [details] File: dso_list
Created attachment 707608 [details] File: environ
Created attachment 707609 [details] File: limits
Created attachment 707610 [details] File: maps
Created attachment 707611 [details] File: open_fds
Created attachment 707612 [details] File: proc_pid_status
Created attachment 707613 [details] File: smolt_data
Created attachment 707614 [details] File: var_log_messages
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.