Application: konsole (2.5.4) KDE Platform Version: 4.5.5 (KDE 4.5.5) Qt Version: 4.7.0 Operating System: Linux 2.6.35-30-generic i686 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: I was using Vim to edit my code. And there is another tab with no program running. I have another 2 konsoles in virtual desktop 2 and 3. Music On Console was runing on the konsole on virtual desktop 2 , and there are no programs running on the konsole on virtual desktop 3. When I pressed "Ctrl+Shift+T" to create a new tab , it crashed. Also , konsoles in virtual desktop 2 and 3 closed unexpectedly. But "Music On Console" continued playing music,so it couldn't be the bug of MOC. I can't reproduce the bug. But sometimes konsole crashed when I did some similar things like above. The crash can be reproduced some of the time. -- Backtrace: Application: Konsole (konsole), signal: Aborted [Current thread is 1 (Thread 0xb7893710 (LWP 3592))] Thread 2 (Thread 0xaf97db70 (LWP 3623)): #0 0x00786416 in __kernel_vsyscall () #1 0x00f37df6 in poll () from /lib/libc.so.6 #2 0x02313a1b in g_poll () from /lib/libglib-2.0.so.0 #3 0x0230643c in ?? () from /lib/libglib-2.0.so.0 #4 0x02306848 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0116559f in QEventDispatcherGlib::processEvents (this=0x9738210, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #6 0x01135609 in QEventLoop::processEvents (this=0xaf97d290, flags=) at kernel/qeventloop.cpp:149 #7 0x01135a8a in QEventLoop::exec (this=0xaf97d290, flags=...) at kernel/qeventloop.cpp:201 #8 0x01031b7e in QThread::exec (this=0x9733cc8) at thread/qthread.cpp:490 #9 0x0111435b in QInotifyFileSystemWatcherEngine::run (this=0x9733cc8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x01034df9 in QThreadPrivate::start (arg=0x9733cc8) at thread/qthread_unix.cpp:266 #11 0x00209cc9 in start_thread () from /lib/libpthread.so.0 #12 0x00f4669e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb7893710 (LWP 3592)): [KCrash Handler] #7 0x00786416 in __kernel_vsyscall () #8 0x00ea0941 in raise () from /lib/libc.so.6 #9 0x00ea3e42 in abort () from /lib/libc.so.6 #10 0x001be055 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #11 0x001bbf35 in ?? () from /usr/lib/libstdc++.so.6 #12 0x001bbf72 in std::terminate() () from /usr/lib/libstdc++.so.6 #13 0x001bcb85 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6 #14 0x01428b1f in QApplication::x11ProcessEvent (this=0xbfa29ae4, event=0xbfa2974c) at kernel/qapplication_x11.cpp:3316 #15 0x0145936a in x11EventSourceDispatch (s=0x9265f00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #16 0x02302855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #17 0x02306668 in ?? () from /lib/libglib-2.0.so.0 #18 0x02306848 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #19 0x01165565 in QEventDispatcherGlib::processEvents (this=0x9243688, flags=...) at kernel/qeventdispatcher_glib.cpp:415 #20 0x01458be5 in QGuiEventDispatcherGlib::processEvents (this=0x9243688, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #21 0x01135609 in QEventLoop::processEvents (this=0xbfa29a44, flags=) at kernel/qeventloop.cpp:149 #22 0x01135a8a in QEventLoop::exec (this=0xbfa29a44, flags=...) at kernel/qeventloop.cpp:201 #23 0x0113a00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #24 0x01395e07 in QApplication::exec () at kernel/qapplication.cpp:3672 #25 0x002b36ab in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_konsole.so #26 0x080485ab in _start () Possible duplicates by query: bug 275126, bug 275018, bug 274935, bug 274685, bug 274499. Reported using DrKonqi
Unfortunately, the backtrace does not contain useful konsole-related info. It looks more like a bug of Qt.