Version: (using KDE 3.5.9) Installed from: Fedora RPMs OS: Linux Hello together, here's a crash log from kicker that sometimes happens during shutdown. It does not crash every time but every second day. The bug was already existing in KDE 3.5.8 so I waited for KDE 3.5.9 to see if it is fixed. Here's the backtrace: Getting all the debuginfos: debuginfo-install kdebase (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) ... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208600352 (LWP 2772)] (no debugging symbols found) ... (no debugging symbols found) [KCrash handler] #5 0x07280a1e in TaskContainer::popupMenu () from /usr/lib/libtaskbar.so.1 #6 0x072860a0 in TaskContainer::performAction () from /usr/lib/libtaskbar.so.1 #7 0x0728c16c in TaskContainer::mousePressEvent () from /usr/lib/libtaskbar.so.1 #8 0x01151373 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #9 0x010ab4eb in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #10 0x010acc99 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #11 0x00dc23a2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #12 0x010423c6 in QETWidget::translateMouseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #13 0x01041196 in QApplication::x11ProcessEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #14 0x01052e1b in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #15 0x010c4dc0 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #16 0x010c4c76 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #17 0x010ab12f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #18 0x00188202 in ?? () #19 0x095ce440 in ?? () #20 0xbfdddd18 in ?? () #21 0xbfdddcd8 in ?? () #22 0xbfdddcd0 in ?? () #23 0x00000000 in ?? () The crash occurs when KDE is already shutting down. Hope the backtrace is any help. Thanks in advance, Thomas
*** This bug has been marked as a duplicate of 121430 ***
*** Bug 163361 has been marked as a duplicate of this bug. ***