Hi folks I did update to the newest release in 0.12 branch, now scenario looks like this: 3 accounts, MSN, jabber, gadu. start kopete. go to the traybar menu -> change status -> online. I can see 3 accounts are starting to connect. Now sometimes ppl leave me mesgs while I am offline, this time jabber server reported to me that someone registered new account. I get the baloon, and now the app freezes. Can't click on anything, it is dead. Same happends if someone will leave me mesg on gadu. Here's .xsession-errors |grep kopete, just before the freeze:
kopete: [void ChatWindowStyle::readStyleFiles()] Header HTML: kopete: [void ChatWindowStyle::readStyleFiles()] Footer HTML: kopete: [void ChatWindowStyle::readStyleFiles()] Incoming HTML: <div class="KopeteMessage"> kopete: [void ChatWindowStyle::readStyleFiles()] NextIncoming HTML: <div class="NextIncomingMessage"><img src="images/body-inbound-arrow.png" style="padding-bottom: 2px; vertical-align: middle;"/>%message%</div> kopete: kopete: [void ChatWindowStyle::readStyleFiles()] Outgoing HTML: <div class="KopeteMessage"> kopete: kopete: [void ChatWindowStyle::readStyleFiles()] NextOutgoing HTML: <div class="NextOutgoingMessage"><img src="images/body-outbound-arrow.png" style="padding-bottom: 2px; vertical-align: middle;"/>%message%</div> kopete: kopete: [void ChatWindowStyle::readStyleFiles()] Status HTML: <div class="KopeteMessage"> kopete: [void ChatWindowStyle::readStyleFiles()] ActionIncoming HTML: <div class="KopeteMessage"> kopete: kopete: [void ChatWindowStyle::readStyleFiles()] ActionOutgoing HTML: <div class="KopeteMessage"> kopete: kopete: [void ChatMessagePart::writeTemplate()] libkopete: WARNING: Failed to cast view to QObject * kopete: [void ChatMessagePart::writeTemplate()] libkopete: [void KopeteSystemTray::addBalloon()] msg text=... <a href="mailto:[EMAIL PROTECTED]" title="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED] </a> ... libkopete: [virtual Kopete::MessageEvent::~MessageEvent()] kopete (history): [void HistoryLogger::saveToDisk()] /home/gj/.kde/share/apps/kopete/logs/JabberProtocol/[EMAIL PROTECTED]/blah-com-pl.200604.xml saved in 222 ms kopete (jabber): [void JabberContact::slotGetTimedVCard()] Requesting vCard for [EMAIL PROTECTED] from update timer. kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get" to="[EMAIL PROTECTED]" id="aaeca" > kopete (jabber - raw protocol): At this moment in time my patience timer runs to zero, and I do alt+f2 : and killall -SIGSEGV kopete kdesktop (Minicli): Arguments: -SIGSEGV kopete kdesktop (Minicli): Arguments: -SIGSEGV kopete KCrash: Application Name = kopete path = <unknown> pid = 21957 DCOP: unregister 'kopete' kimproxy (kdelibs): kopete quit, removing its presence info. now here's the bt: Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241889088 (LWP 21957)] [New Thread -1285391440 (LWP 21984)] [New Thread -1276675152 (LWP 21982)] [New Thread -1268286544 (LWP 21981)] [New Thread -1251509328 (LWP 21979)] [KCrash handler] #5 0xb63d0199 in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0 #6 0xb63ccf07 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0 #7 0xbfe7a7e8 in ?? () #8 0xbfe7a790 in ?? () #9 0xb7e14a78 in ?? () #10 0xb747277b in ?? () from /opt/kde/lib/libkdecore.so.4 #11 0x03c0ae82 in ?? () #12 0xb6aa7ff4 in ?? () from /lib/tls/libc.so.6 #13 0xbfe7a788 in ?? () #14 0x08437aa0 in ?? () #15 0xbfe7a718 in ?? () #16 0xb6a53086 in pthread_mutex_lock () from /lib/tls/libc.so.6 #17 0xb6a53086 in pthread_mutex_lock () from /lib/tls/libc.so.6 #18 0xb718cef2 in QRealMutexPrivate::lock () from /usr/share/qt3/lib/libqt-mt.so.3 #19 0xb718cc42 in QMutex::lock () from /usr/share/qt3/lib/libqt-mt.so.3 #20 0xb7609876 in QMutexLocker (this=0xfffffffc, m=0xb63d4ff4) at qmutex.h:96 #21 0xb760a79f in KNetwork::Internal::KResolverManager::dequeue (this=0x55c5, obj=0xfffffffc) at /home/gj/kde-sources/kdelibs/kdecore/network/kresolvermanager.cpp:820 #22 0xb7608c42 in KNetwork::KResolver::cancel (this=0x83c10e4, emitSignal=false) at /home/gj/kde-sources/kdelibs/kdecore/network/kresolver.cpp:510 #23 0xb75b4112 in KExtendedSocket::release (this=0x83dc1e0) at /home/gj/kde-sources/kdelibs/kdecore/kextsock.cpp:1328 #24 0xb7525b42 in KServerSocket::slotAccept (this=0x875b190) at /home/gj/kde-sources/kdelibs/kdecore/ksock.cpp:417 #25 0xb7526169 in KServerSocket::qt_invoke (this=0x875b190, _id=2, _o=0xbfe7a8f8) at ksock.moc:262 #26 0xb6eaf92c in QObject::activate_signal () from /usr/share/qt3/lib/libqt-mt.so.3 #27 0xb6eb0106 in QObject::activate_signal () from /usr/share/qt3/lib/libqt-mt.so.3 #28 0xb723e1f7 in QSocketNotifier::activated () from /usr/share/qt3/lib/libqt-mt.so.3 #29 0xb6ecfaaa in QSocketNotifier::event () from /usr/share/qt3/lib/libqt-mt.so.3 #30 0xb6e46122 in QApplication::internalNotify () from /usr/share/qt3/lib/libqt-mt.so.3 #31 0xb6e46314 in QApplication::notify () from /usr/share/qt3/lib/libqt-mt.so.3 #32 0xb74e8aa9 in KApplication::notify (this=0xbfe7aee0, receiver=0x83b67b0, event=0xbfe7ac50) at /home/gj/kde-sources/kdelibs/kdecore/kapplication.cpp:550 #33 0xb779e30e in QApplication::sendEvent (receiver=0xb63d4ff4, event=0xbfe7ac50) at qapplication.h:520 #34 0xb6e37cdd in QEventLoop::activateSocketNotifiers () from /usr/share/qt3/lib/libqt-mt.so.3 #35 0xb6deb542 in QEventLoop::processEvents () from /usr/share/qt3/lib/libqt-mt.so.3 #36 0xb6e5eb01 in QEventLoop::enterLoop () from /usr/share/qt3/lib/libqt-mt.so.3 #37 0xb6e5ea26 in QEventLoop::exec () from /usr/share/qt3/lib/libqt-mt.so.3 #38 0xb6e44c35 in QApplication::exec () from /usr/share/qt3/lib/libqt-mt.so.3 #39 0x080747e7 in main (argc=-4, argv=0xfffffffc) at /home/gj/kde-sources/kopete/0.12/kopete/kopete/main.cpp:107 quite vague, but clearly shows that it is the KDE resolver (again), this used to happend long long time ago, and Thiago was trying to fix/fixed it. Why do I blame MSN ? because it is the only protocol left, and if I don't start up MSN, everything works very well. Ta. -- GJ _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
