Version: 3.5.x branch from 06.09.07 (using KDE Devel) Installed from: Compiled sources Compiler: gcc 4.1.3 Debian testing OS: Linux Hi, since today my kopete crashes during startup and connecting to MSN. Ueseing a Jabber transport to MSN works with the same account. Here is a backtrace: Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241905472 (LWP 31560)] [KCrash handler] #6 0xb4a94e40 in MSNNotifySocket::disconnectReason (this=0x0) at msnnotifysocket.h:72 #7 0xb4a91f40 in MSNAccount::slotNotifySocketClosed (this=0x8687330) at msnaccount.cpp:408 #8 0xb4a93013 in MSNAccount::qt_invoke (this=0x8687330, _id=33, _o=0xbffcdc1c) at msnaccount.moc:227 #9 0xb67fcb06 in QObject::activate_signal (this=0x8b26cc8, clist=0x8a1bab0, o=0xbffcdc1c) at kernel/qobject.cpp:2356 #10 0xb67fd72f in QObject::activate_signal (this=0x8b26cc8, signal=5) at kernel/qobject.cpp:2325 #11 0xb4a9cc89 in MSNSocket::socketClosed (this=0x8b26cc8) at msnsocket.moc:204 #12 0xb4ab3e24 in MSNNotifySocket::disconnect (this=0x8b26cc8) at msnnotifysocket.cpp:101 #13 0xb4aaa839 in MSNNotifySocket::sslLoginFailed (this=0x8b26cc8) at msnnotifysocket.cpp:673 #14 0xb4aafc62 in MSNNotifySocket::qt_invoke (this=0x8b26cc8, _id=22, _o=0xbffcdd3c) at msnnotifysocket.moc:387 #15 0xb67fcb06 in QObject::activate_signal (this=0x8aa9748, clist=0x8b21540, o=0xbffcdd3c) at kernel/qobject.cpp:2356 #16 0xb67fd72f in QObject::activate_signal (this=0x8aa9748, signal=4) at kernel/qobject.cpp:2325 #17 0xb4ac5361 in MSNSecureLoginHandler::loginFailed (this=0x8aa9748) at msnsecureloginhandler.moc:113 #18 0xb4ac56af in MSNSecureLoginHandler::slotTweenerReceived (this=0x8aa9748, authJob=0x8b56418) at msnsecureloginhandler.cpp:128 #19 0xb4ac5e21 in MSNSecureLoginHandler::qt_invoke (this=0x8aa9748, _id=3, _o=0xbffcde64) at msnsecureloginhandler.moc:120 #20 0xb67fcb06 in QObject::activate_signal (this=0x8b56418, clist=0x8aae250, o=0xbffcde64) at kernel/qobject.cpp:2356 #21 0xb741ffb2 in KIO::Job::result (this=0x8b56418, t0=0x8b56418) at jobclasses.moc:162 #22 0xb7425f3d in KIO::Job::emitResult (this=0x8b56418) at job.cpp:235 #23 0xb742659c in KIO::SimpleJob::slotFinished (this=0x8b56418) at job.cpp:601 #24 0xb742692d in KIO::TransferJob::slotFinished (this=0x8b56418) at job.cpp:971 #25 0xb74248f9 in KIO::SimpleJob::qt_invoke (this=0x8b56418, _id=7, _o=0xbffce1c4) at jobclasses.moc:417 #26 0xb7424c39 in KIO::TransferJob::qt_invoke (this=0x8b56418, _id=7, _o=0xbffce1c4) at jobclasses.moc:1082 #27 0xb67fcb06 in QObject::activate_signal (this=0x8254730, clist=0x8b565c0, o=0xbffce1c4) at kernel/qobject.cpp:2356 #28 0xb6b09064 in QSignal::signal (this=0x8254730, t0=@0x8254758) at .moc/debug-shared-mt/moc_qsignal.cpp:100 #29 0xb68179e5 in QSignal::activate (this=0x8254730) at kernel/qsignal.cpp:212 #30 0xb681e35f in QSingleShotTimer::event (this=0x8254708) at kernel/qtimer.cpp:286 #31 0xb67a25d1 in QApplication::internalNotify (this=0xbffce65c, receiver=0x8254708, e=0xbffce464) at kernel/qapplication.cpp:2635 #32 0xb67a33bd in QApplication::notify (this=0xbffce65c, receiver=0x8254708, e=0xbffce464) at kernel/qapplication.cpp:2358 #33 0xb6e0db13 in KApplication::notify (this=0xbffce65c, receiver=0x8254708, event=0xbffce464) at kapplication.cpp:550 #34 0xb6798741 in QEventLoop::activateTimers (this=0x817bae8) at kernel/qapplication.h:496 #35 0xb67548c4 in QEventLoop::processEvents (this=0x817bae8, flags=4) at kernel/qeventloop_x11.cpp:389 #36 0xb67b8356 in QEventLoop::enterLoop (this=0x817bae8) at kernel/qeventloop.cpp:198 #37 0xb67b8228 in QEventLoop::exec (this=0x817bae8) at kernel/qeventloop.cpp:145 #38 0xb67a2134 in QApplication::exec (this=0xbffce65c) at kernel/qapplication.cpp:2758 #39 0x08076be0 in main (argc=143989776, argv=0x0) at main.cpp:107
Hmm, the SVN update and rebuild of KDE last night solved the problem.
This bug fixed , but the fix not working until now !! 2008-3-15