Version: 1.5.4 (using KDE 3.1.4) Installed from: SuSE Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-144-default crashed after entering the passphrase before displaying PGP/GnuPG message (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 2529)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x4182ba86 in waitpid () from /lib/i686/libpthread.so.0 #0 0x4182ba86 in waitpid () from /lib/i686/libpthread.so.0 #1 0x40d0fd30 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x4182a96c in __pthread_sighandler () from /lib/i686/libpthread.so.0 #3 <signal handler called> #4 0x081ddc62 in partNode::nodeId() () #5 0x0813543b in KMReaderWin::parseObjectTree(KMReaderWin*, QCString*, CryptPlugWrapper*, partNode*, bool, bool, bool) () #6 0x08135634 in KMReaderWin::parseObjectTree(KMReaderWin*, QCString*, CryptPlugWrapper*, partNode*, bool, bool, bool) () #7 0x08136bba in KMReaderWin::parseObjectTree(KMReaderWin*, QCString*, CryptPlugWrapper*, partNode*, bool, bool, bool) () #8 0x081450aa in KMReaderWin::parseMsg(KMMessage*, bool) () #9 0x0813fcde in KMReaderWin::parseMsg() () #10 0x0813d765 in KMReaderWin::updateReaderWin() () #11 0x08154dd8 in KMReaderWin::qt_invoke(int, QUObject*) () #12 0x4110769b in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0x41107464 in QObject::activate_signal(int) () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0x414382f9 in QTimer::timeout() () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0x41129a73 in QTimer::event(QEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0x410a56d6 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0x410a49fe in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0x40c9d5e9 in KApplication::notify(QObject*, QEvent*) () from /opt/kde3/lib/libkdecore.so.4 #19 0x41091bd3 in QEventLoop::activateTimers() () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0x4104d29d in QEventLoop::processEvents(unsigned) () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0x410b9980 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0x410b9876 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0x410a596f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0x081b674d in main ()
Most likely a duplicate of bug #53185. At least the backtrace looks very similar. *** This bug has been marked as a duplicate of 53185 ***
I noticed a similar bug (first time in years that Kmail has crashed on me!) that started the same way but thereafter every mail whether composed fresh or as a reply with or without being signed would cause a crash. Workaround that helped me was to log out of KDE and back in again. Everything is fine now.