Version: my KDE is 3.5.2, but kmail and its dependencies were upgraded to 3.5.7 with the gentoo portage split KDE scheme (using KDE KDE 3.5.7) Installed from: Gentoo Packages OS: Linux kmail crashed while composing a message [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1249478992 (LWP 10335)] [New Thread -1279202400 (LWP 10343)] [New Thread -1270809696 (LWP 10342)] [New Thread -1262416992 (LWP 10341)] [New Thread -1254024288 (LWP 10340)] [KCrash handler] #6 0xb7be0353 in MessageComposer::emitDone (this=0xab71d98, b=false) at messagecomposer.cpp:364 #7 0xb7be0418 in MessageComposer::doNextJob (this=0xab71d98) at messagecomposer.cpp:352 #8 0xb7dbb955 in MessageComposer::applyChanges (this=0xab71d98, disableCrypto=true) at messagecomposer.cpp:333 #9 0xb7dbbb7f in KMComposeWin::applyChanges (this=0xaa84910, dontSignNorEncrypt=true, dontDisable=true) at kmcomposewin.cpp:2219 #10 0xb7dbbe03 in KMComposeWin::autoSaveMessage (this=0xaa84910) at kmcomposewin.cpp:717 #11 0xb7de806e in KMComposeWin::qt_invoke (this=0xaa84910, _id=147, _o=0xbfe1830c) at kmcomposewin.moc:508 #12 0xb5ba1a5f in QObject::activate_signal (this=0xaa756b0, clist=0xaae04e0, o=0xbfe1830c) at qobject.cpp:2356 #13 0xb5ba27f8 in QObject::activate_signal (this=0xaa756b0, signal=2) at qobject.cpp:2325 #14 0xb5fa18e6 in QTimer::timeout (this=0xaa756b0) at moc_qtimer.cpp:82 #15 0xb5bd0365 in QTimer::event (this=0xaa756b0, e=0xbfe18668) at qtimer.cpp:219 #16 0xb5b2d1eb in QApplication::internalNotify (this=0xbfe190d0, receiver=0xaa756b0, e=0xbfe18668) at qapplication.cpp:2635 #17 0xb5b2f163 in QApplication::notify (this=0xbfe190d0, receiver=0xaa756b0, e=0xbfe18668) at qapplication.cpp:2358 #18 0xb6417b54 in KApplication::notify (this=0xbfe190d0, receiver=0xaa756b0, event=0xbfe18668) at kapplication.cpp:550 #19 0xb707443e in QApplication::sendEvent (receiver=0xaa756b0, event=0xbfe18668) at qapplication.h:496 #20 0xb5b1dfc0 in QEventLoop::activateTimers (this=0x80fe090) at qeventloop_unix.cpp:556 #21 0xb5acd3ab in QEventLoop::processEvents (this=0x80fe090, flags=4) at qeventloop_x11.cpp:389 #22 0xb5b4b205 in QEventLoop::enterLoop (this=0x80fe090) at qeventloop.cpp:198 #23 0xb5b2ee2d in QApplication::enter_loop (this=0xbfe190d0) at qapplication.cpp:2793 #24 0xb7dbbe13 in KMComposeWin::autoSaveMessage (this=0x9688240) at kmcomposewin.cpp:720 #25 0xb7de806e in KMComposeWin::qt_invoke (this=0x9688240, _id=147, _o=0xbfe18aec) at kmcomposewin.moc:508 #26 0xb5ba1a5f in QObject::activate_signal (this=0xaabc180, clist=0xaaea790, o=0xbfe18aec) at qobject.cpp:2356 #27 0xb5ba27f8 in QObject::activate_signal (this=0xaabc180, signal=2) at qobject.cpp:2325 #28 0xb5fa18e6 in QTimer::timeout (this=0xaabc180) at moc_qtimer.cpp:82 #29 0xb5bd0365 in QTimer::event (this=0xaabc180, e=0xbfe18e48) at qtimer.cpp:219 #30 0xb5b2d1eb in QApplication::internalNotify (this=0xbfe190d0, receiver=0xaabc180, e=0xbfe18e48) at qapplication.cpp:2635 #31 0xb5b2f163 in QApplication::notify (this=0xbfe190d0, receiver=0xaabc180, e=0xbfe18e48) at qapplication.cpp:2358 #32 0xb6417b54 in KApplication::notify (this=0xbfe190d0, receiver=0xaabc180, event=0xbfe18e48) at kapplication.cpp:550 #33 0xb707443e in QApplication::sendEvent (receiver=0xaabc180, event=0xbfe18e48) at qapplication.h:496 #34 0xb5b1dfc0 in QEventLoop::activateTimers (this=0x80fe090) at qeventloop_unix.cpp:556 #35 0xb5acd3ab in QEventLoop::processEvents (this=0x80fe090, flags=4) at qeventloop_x11.cpp:389 #36 0xb5b4b205 in QEventLoop::enterLoop (this=0x80fe090) at qeventloop.cpp:198 #37 0xb5b4b026 in QEventLoop::exec (this=0x80fe090) at qeventloop.cpp:145 #38 0xb5b2eeaf in QApplication::exec (this=0xbfe190d0) at qapplication.cpp:2758 #39 0x0804a925 in main (argc=178774704, argv=0xab34f28) at main.cpp:110
This is almost certainly the same problem as the one you reported earlier in bug 147016. *** This bug has been marked as a duplicate of 147016 ***