Version: (using KDE 4.1.3) Installed from: Ubuntu Packages This is a weird one... I had a konsole open and I left it unused on a virtual desktop for several hours after using it for a while. When I returned to the virtual desktop in order to use the konsole, I typed "cd<ENTER>" in the konsole and immediately the konsole crashed with signal 6. Here is the debugging backtrace: ---- Application: Konsole (konsole), signal SIGABRT (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7fc81654b6f0 (LWP 8186)] [New Thread 0x40aef950 (LWP 8187)] [KCrash handler] #5 0x00007fc815d2dfd5 in raise () from /lib/libc.so.6 #6 0x00007fc815d2fb43 in abort () from /lib/libc.so.6 #7 0x00007fc8148066b5 in qt_message_output () from /usr/lib/libQtCore.so.4 #8 0x00007fc8148067fd in qFatal () from /usr/lib/libQtCore.so.4 #9 0x00007fc81610ee86 in ?? () from /usr/lib/libkdeinit4_konsole.so #10 0x00007fc816112bca in ?? () from /usr/lib/libkdeinit4_konsole.so #11 0x00007fc81611398d in ?? () from /usr/lib/libkdeinit4_konsole.so #12 0x00007fc81490b134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0x00007fc8160f044d in ?? () from /usr/lib/libkdeinit4_konsole.so #14 0x00007fc81490b134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0x00007fc8160c5bce in ?? () from /usr/lib/libkdeinit4_konsole.so #16 0x00007fc8160c5dd8 in ?? () from /usr/lib/libkdeinit4_konsole.so #17 0x00007fc8161283a5 in ?? () from /usr/lib/libkdeinit4_konsole.so #18 0x00007fc81490b134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #19 0x00007fc814905a43 in QObject::event () from /usr/lib/libQtCore.so.4 #20 0x00007fc813483c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0x00007fc81348b9ba in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0x00007fc815252fcb in KApplication::notify (this=0x7fff1e57cbf0, receiver=0x29d88a0, event=0x7fff1e57c890) at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311 #23 0x00007fc8148f6d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0x00007fc814922ab6 in ?? () from /usr/lib/libQtCore.so.4 #25 0x00007fc81491f1fd in ?? () from /usr/lib/libQtCore.so.4 #26 0x00007fc81057dd3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0x00007fc81058150d in ?? () from /usr/lib/libglib-2.0.so.0 #28 0x00007fc8105816cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0x00007fc81491f15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #30 0x00007fc813515a6f in ?? () from /usr/lib/libQtGui.so.4 #31 0x00007fc8148f5682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #32 0x00007fc8148f580d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #33 0x00007fc8148f7cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #34 0x00007fc81613025b in kdemain () from /usr/lib/libkdeinit4_konsole.so #35 0x00007fc815d19466 in __libc_start_main () from /lib/libc.so.6 #36 0x0000000000400659 in _start () #0 0x00007fc815da3621 in nanosleep () from /lib/libc.so.6 ----
I mistakenly marked this as a bug (i.e., not a crash bug) when I filed it. It's not obvious how I to change the report now, but presumably someone else can mark this as referring to a crash, and not just an ordinary bug.
Have you experienced this bug again using a recent KDE (4.1.4 / 4.2.0 / 4.2svn / 4.3svn) ? Thanks :)
Nope; it seems to have been a one-time occurrence.
Please reopen if you experience this again. Thanks :)