Application that crashed: rosegardensequencer Version of the application: 1.7.3 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.30.9-90.fc11.i586 i686 Distribution: "Fedora release 11 (Leonidas)" -- Backtrace: Application: RosegardenSequencer (rosegardensequencer), signal: Aborted [Current thread is 1 (Thread 0xb7890780 (LWP 7009))] Thread 2 (Thread 0xb7671b70 (LWP 7010)): #0 0x0025e422 in __kernel_vsyscall () #1 0x002defa5 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122 #2 0x007355df in ?? () from /usr/lib/libjack.so.0 #3 0x002da935 in start_thread (arg=0xb7671b70) at pthread_create.c:297 #4 0x00b2c94e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb7890780 (LWP 7009)): [KCrash Handler] #6 0x0025e422 in __kernel_vsyscall () #7 0x00a797c1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0x00a7b092 in *__GI_abort () at abort.c:88 #9 0x00a728ee in *__GI___assert_fail (assertion=0x2a8333c "seq && status", file=0x2a83290 "seq.c", line=3382, function=0x2a83dab "snd_seq_get_queue_status") at assert.c:78 #10 0x02a6459c in snd_seq_get_queue_status (seq=0x0, q=-1, status=0x6) at seq.c:3382 #11 0x08086bfb in Rosegarden::AlsaDriver::getAlsaTime (this=0x9334228) at /usr/src/debug/rosegarden-1.7.3/src/sound/AlsaDriver.cpp:2422 #12 0x08086e29 in Rosegarden::AlsaDriver::shutdown (this=0x9334228) at /usr/src/debug/rosegarden-1.7.3/src/sound/AlsaDriver.cpp:148 #13 0x080a7de8 in Rosegarden::SoundDriverFactory::createDriver (studio=0x929f620) at /usr/src/debug/rosegarden-1.7.3/src/sound/SoundDriverFactory.cpp:44 #14 0x080b0576 in Rosegarden::RosegardenSequencerApp::RosegardenSequencerApp (this=0x92dae18, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/rosegarden-1.7.3/src/sequencer/RosegardenSequencerApp.cpp:98 #15 0x080a94b6 in main (argc=1, argv=0xbfa352f4) at /usr/src/debug/rosegarden-1.7.3/src/sequencer/main.cpp:96 Reported using DrKonqi
Sorry. I now see that my two crashes are the same. *** This bug has been marked as a duplicate of bug 213380 ***