kopete crashes when trying to connect to MSN

[sputnik]

Using Hardy Heron (8.04.1) with KDE 3.5.10
kopete-package: 4:3.5.10-0ubuntu1~hardy1

Kopete can't connect to MSN and crashes while trying.

This was my last output from konsole. I started kopete in offline mode and manually connected only to MSN. (All other services are working well here - I just excluded MSN to connect only manual):

sputnik_$ kopete
sputnik_$ QDateTime::fromString: Parameter out of range
QDateTime::fromString: Parameter out of range
QDateTime::fromString: Parameter out of range
QDateTime::fromString: Parameter out of range
KCrash: Application 'kopete' crashing...

And this is what I could get last time out of the kcrash backtrace:

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5ffa6c0 (LWP 21960)]
[KCrash handler]
#6 0xb67d9052 in QShared::ref (this=0x3) at ../include/qshared.h:52
#7 0xb6bce02d in QString (this=0xbf96c4d8, s=@0x86a54f8)
    at tools/qstring.cpp:1400
#8 0xb7e1300f in Kopete::Contact::contactId () from /usr/lib/libkopete.so.1
#9 0xb557501b in MSNNotifySocket::parseCommand ()
   from /usr/lib/libkopete_msn_shared.so.0
#10 0xb555e52b in MSNSocket::parseLine ()
   from /usr/lib/libkopete_msn_shared.so.0
#11 0xb555ffa2 in MSNSocket::slotReadLine ()
   from /usr/lib/libkopete_msn_shared.so.0
#12 0xb55648f8 in MSNSocket::qt_invoke ()
   from /usr/lib/libkopete_msn_shared.so.0
#13 0xb557203f in MSNNotifySocket::qt_invoke ()
   from /usr/lib/libkopete_msn_shared.so.0
#14 0xb68b5704 in QObject::activate_signal (this=0x81ed300, clist=0x86b9468,
    o=0xbf96c838) at kernel/qobject.cpp:2359
#15 0xb6c44aba in QSignal::signal (this=0x81ed300, t0=@0x81ed328)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#16 0xb68d47b2 in QSignal::activate (this=0x81ed300) at kernel/qsignal.cpp:215
#17 0xb68dc936 in QSingleShotTimer::event (this=0x81ed2d8)
    at kernel/qtimer.cpp:289
#18 0xb6849c36 in QApplication::internalNotify (this=0xbf96ce14,
    receiver=0x81ed2d8, e=0xbf96cb48) at kernel/qapplication.cpp:2638
#19 0xb684ba5f in QApplication::notify (this=0xbf96ce14, receiver=0x81ed2d8,
    e=0xbf96cb48) at kernel/qapplication.cpp:2361
#20 0xb700a9b2 in KApplication::notify (this=0xbf96ce14, receiver=0x81ed2d8,
    event=0xbf96cb48)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#21 0xb67da28d in QApplication::sendEvent (receiver=0x81ed2d8,
    event=0xbf96cb48) at ../include/qapplication.h:523
#22 0xb683cb19 in QEventLoop::activateTimers (this=0x8166390)
    at kernel/qeventloop_unix.cpp:559
#23 0xb67ef64b in QEventLoop::processEvents (this=0x8166390, flags=4)
    at kernel/qeventloop_x11.cpp:392
#24 0xb6864f90 in QEventLoop::enterLoop (this=0x8166390)
    at kernel/qeventloop.cpp:201
#25 0xb6864c8e in QEventLoop::exec (this=0x8166390)
    at kernel/qeventloop.cpp:148
#26 0xb684b7df in QApplication::exec (this=0xbf96ce14)
    at kernel/qapplication.cpp:2761
#27 0x0807fc73 in ?? ()
#28 0xb605d450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#29 0x0806f071 in ?? ()

Thanks for looking at it!

[Andreas Wenning (andreas-wenning)]

Hi sputnik

I can see, that you run the 4:3.5.10-0ubuntu1~hardy1 version (from hardy-backports). If it is possible, please downgrade to version 4:3.5.9-0ubuntu1.1 (from hardy updates) and see if the problem persists? We're interested in if this is a regression from 3.5.9 to 3.5.10 .

[sputnik (sputnik)]

Andreas, I think that this will be a regression as it infact appeared after the upgrade.
I will try to catch the old package, install it and tell about.
Thanks so far.

[Andreas Wenning (andreas-wenning)]

Also try if you can reproduce the crash with the -dbgsym package installed as described here: https://wiki.kubuntu.org/DebuggingProgramCrash

[sputnik (sputnik)]

No regression as it seems.

Also the 4:3.5.9-0ubuntu1.1-package crashed.

[Thread debugging using libthread_db enabled]
[New Thread 0xb604d6c0 (LWP 21703)]
[KCrash handler]
#6 0xb682c052 in QShared::ref (this=0x1) at ../include/qshared.h:52
#7 0xb6c2102d in QString (this=0xbff61448, s=@0x8421110)
    at tools/qstring.cpp:1400
#8 0xb7e65f4f in Kopete::Contact::contactId (this=0x8244ae8)
    at /build/buildd/kdenetwork-3.5.9/./kopete/libkopete/kopetecontact.cpp:483
#9 0xb565101b in MSNNotifySocket::parseCommand (this=0x867cb18,
    cmd=@0xbff6163c, id=6, data=@0xbff61638)
    at /build/buildd/kdenetwork-3.5.9/./kopete/protocols/msn/msnnotifysocket.cpp:369
#10 0xb563a52b in MSNSocket::parseLine (this=0x867cb18, str=@0xbff61698)
    at /build/buildd/kdenetwork-3.5.9/./kopete/protocols/msn/msnsocket.cpp:526
#11 0xb563bfa2 in MSNSocket::slotReadLine (this=0x867cb18)
    at /build/buildd/kdenetwork-3.5.9/./kopete/protocols/msn/msnsocket.cpp:456
#12 0xb563e23d in MSNSocket::slotDataReceived (this=0x867cb18)
    at /build/buildd/kdenetwork-3.5.9/./kopete/protocols/msn/msnsocket.cpp:411
#13 0xb564089d in MSNSocket::qt_invoke (this=0x867cb18, _id=9, _o=0xbff619c8)
    at ./msnsocket.moc:231
#14 0xb564e03f in MSNNotifySocket::qt_invoke (this=0x867cb18, _id=9,
    _o=0xbff619c8) at ./msnnotifysocket.moc:391
#15 0xb6908704 in QObject::activate_signal (this=0x866c160, clist=0x84e2a00,
    o=0xbff619c8) at kernel/qobject.cpp:2359
#16 0xb69091e9 in QObject::activate_signal (this=0x866c160, signal=9)
    at kernel/qobject.cpp:2328
#17 0xb708ab8c in KNetwork::KClientSocketBase::readyRead (this=0x866c160)
    at ./kclientsocketbase.moc:192
#18 0xb708abc6 in KNetwork::KClientSocketBase::slotReadActivity (this=0x1)
    at /build/buildd/kdelibs-3.5.10/./kdecore/network/kclientsocketbase.cpp:416
#19 0xb7090378 in KNetwork::KBufferedSocket::slotReadActivity (this=0x866c160)
    at /build/buildd/kdelibs-3.5.10/./kdecore/network/kbufferedsocket.cpp:354
#20 0xb709e399 in KNetwork::KBufferedSocket::qt_invoke (this=0x866c160,
    _id=8, _o=0xbff61af0) at ./kbufferedsocket.moc:97
#21 0xb6908704 in QObject::activate_signal (this=0x866c088, clist=0x84da700,
    o=0xbff61af0) at kernel/qobject.cpp:2359
#22 0xb6909051 in QObject::activate_signal (this=0x866c088, signal=2,
    param=13) at kernel/qobject.cpp:2452
#23 0xb6c98b99 in QSocketNotifier::activated (this=0x866c088, t0=13)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#24 0xb692a766 in QSocketNotifier::event (this=0x866c088, e=0xbff61e00)
    at kernel/qsocketnotifier.cpp:261
#25 0xb689cc36 in QApplication::internalNotify (this=0xbff620c4,
    receiver=0x866c088, e=0xbff61e00) at kernel/qapplication.cpp:2638
#26 0xb689ea5f in QApplication::notify (this=0xbff620c4, receiver=0x866c088,
    e=0xbff61e00) at kernel/qapplication.cpp:2361
#27 0xb705d9b2 in KApplication::notify (this=0xbff620c4, receiver=0x866c088,
    event=0xbff61e00)
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#28 0xb682d28d in QApplication::sendEvent (receiver=0x866c088,
    event=0xbff61e00) at ../include/qapplication.h:523
#29 0xb688eb4a in QEventLoop::activateSocketNotifiers (this=0x8168100)
    at kernel/q...

[Andreas Wenning (andreas-wenning)]

While keeping the -dbgsym package can I have you test with the kdenetwork-dbg package installed and provide all the terminal output?

[sputnik (sputnik)]

Andreas,

I have to know first which version of kdenetwork this should be. All packages of KDE 3.5.9 or nor now the packages for 3.5.10?

apt tells me that kopete for 3.5.9 will be removed if I would install the kdenetwork-dbg-package. I guess I could install that package together with the actual kopete or try to replace the actual kdenetwork with the 3.5.9 version.

What do you like to make me try out?

[sputnik (sputnik)]

Andreas, the kdenetwork-dbg pagacke wants to uninstall the -dbgsym package. I was not able to find a kdenetwork-dbgsym package...

The only konsole output that I was able to get is:
$ kopete
$ QDateTime::fromString: Parameter out of range
QDateTime::fromString: Parameter out of range
QDateTime::fromString: Parameter out of range
QDateTime::fromString: Parameter out of range

for the start of kopete. - But the conection to MSN itself only adds this part:

KCrash: Application 'kopete' crashing...

I attach the output of kopete 3.5.9 with kdenetwork 3.5.9 which I installed manually.

Thanks so far, feel free to give me more hints for testing...!

[Andreas Wenning (andreas-wenning)]

I've digged a bit in the source code, and the problems seems to occur due to an empty (or otherwise strange) contactID on a MSN contact. Have you resently added any contacts with a MSN contactID that could be classified as special? Maybe logging into the account from another client (like amsn/pidgin) and looking through the contacts could reveal one?

[Andreas Wenning (andreas-wenning)]

It looks like kopete saves the contactlist in ~/.kde/share/apps/kopete/contactlist.xml ; try to look through the contacts there too, and look for strange/emty/missing contactIDs?

[sputnik (sputnik)]

Interesting, Andreas!

... see: The last thing I was doing on MSN that I can remember was that I added a new contact. This contact did not accept me as long as I have been online... Maybe there is a notification waiting for me?

So: This contact doesn't have a special MSN-identity, but ... I have... but only in so far that I do not have a hotmail-account as MSN-ident...

[sputnik (sputnik)]

The mentioned xml-file looks boring normal, sorry...

[Andreas Wenning (andreas-wenning)]

I found the bug upstream at https://bugs.kde.org/show_bug.cgi?id=138494 .

In this bug report they mention renaming the ~/.kde/share/apps/kopete/contactlist.xml as a workaround; and this seems to work for everyone there; so might be worth testing.

If it works renaming it they also specifically asks for an example of a broken ~/.kde/share/apps/kopete/contactlist.xml

[sputnik (sputnik)]

Andreas,

thanks for researching work! - At least kopete doesn't crash anymore!!

I moved the ~/.kde/share/apps/kopete/contactlist.xml to a different place, connected - and I was able to connect to MSN! - Now, after moving the xml file back everything looks normal.

However: The output on the command line looks somehow interesting:

sputnik@20:35*~_$ kopete &
[1] 14617
sputnik@20:35*~_$ QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (Die Gegenstelle hat die Verbindung beendet)
Transfer ACCEPTED by: LoginTask
Transfer ACCEPTED by: LoginTask
kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)
Transfer ACCEPTED by: ListTask
CLIENT: RequestPictureTask: Task::done()
CLIENT: RequestPictureTask: emitting finished
Transfer ACCEPTED by: StatusNotifierTask
CLIENT: RequestPictureTask: Task::done()
CLIENT: RequestPictureTask: emitting finished
Transfer ACCEPTED by: StatusNotifierTask
Transfer ACCEPTED by: MailNotifierTask
kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)
QObject::connect: No such signal JabberChatSession::typing(bool)
QObject::connect: (sender name: 'editPart')
QObject::connect: (receiver name: 'unnamed')
libkopete: WARNING: Failed to cast view to QObject *
CLIENT: SendPictureTask: Task::done()
CLIENT: SendPictureTask: emitting finished
Transfer ACCEPTED by: PictureNotifierTask
CLIENT: SendPictureTask: Task::done()
CLIENT: SendPictureTask: emitting finished
Transfer ACCEPTED by: PictureNotifierTask
QGArray::find: Index 0 out of range
Transfer ACCEPTED by: PictureNotifierTask
Transfer ACCEPTED by: PictureNotifierTask
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0!
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (Die Gegenstelle hat die Verbindung beendet)
Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0!
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (Die Gegenstelle hat die Verbindung beendet)
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::disconnect: No such signal Client::gotBuddyIconRequest(const QString&)
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished

[1]+ Done kopete
sputnik@20:39*~_$

Thanks so far!!
I will now continue the t...

[Jonathan Thomas (echidnaman)]

Fix committed for KDE 4.2.

[Jonathan Thomas (echidnaman)]

Fix released to Jaunty. (As well as Intrepid via the kubuntu-experimental ppa packages)

[bbg5ne (webcreator)]

I've kubuntu 8.10

Applicazione: Kopete (kopete), segnale SIGABRT
[Current thread is 0 (LWP 11718)]

Thread 2 (Thread 0xb19cab90 (LWP 12097)):
#0 0xb7fc8430 in __kernel_vsyscall ()
#1 0xb5e34075 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6200bbd in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3 0xb6d3a6f2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4 0xb75c1532 in ?? () from /usr/lib/libQtNetwork.so.4
#5 0xb6d396ae in ?? () from /usr/lib/libQtCore.so.4
#6 0xb5e3050f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb61f2a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb57db6c0 (LWP 11718)):
[KCrash Handler]
#6 0xb7fc8430 in __kernel_vsyscall ()
#7 0xb613c8a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb613e268 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb6361778 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6
#10 0xb635f655 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb635f692 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb635f7ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0xb312bbfb in MSN::Message::getFormatInfo () from /usr/lib/libmsn.so.0.1
#14 0xb312d998 in MSN::Message::getFontName () from /usr/lib/libmsn.so.0.1
#15 0xb31f504b in ?? () from /usr/lib/kde4/kopete_wlm.so
#16 0xb3134717 in MSN::SwitchboardServerConnection::message_plain () from /usr/lib/libmsn.so.0.1
#17 0xb313a52b in MSN::SwitchboardServerConnection::handle_MSG () from /usr/lib/libmsn.so.0.1
#18 0xb31358df in MSN::SwitchboardServerConnection::dispatchCommand () from /usr/lib/libmsn.so.0.1
#19 0xb3134dbd in MSN::SwitchboardServerConnection::handleIncomingData () from /usr/lib/libmsn.so.0.1
#20 0xb3130279 in MSN::Connection::dataArrivedOnSocket () from /usr/lib/libmsn.so.0.1
#21 0xb31f73f1 in ?? () from /usr/lib/kde4/kopete_wlm.so
#22 0xb31f7545 in ?? () from /usr/lib/kde4/kopete_wlm.so
#23 0xb6e3ea60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb6e3f7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb6e77847 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#26 0xb75f14e7 in ?? () from /usr/lib/libQtNetwork.so.4
#27 0xb75f5e9e in QSslSocket::qt_metacall () from /usr/lib/libQtNetwork.so.4
#28 0xb31f751a in ?? () from /usr/lib/kde4/kopete_wlm.so
#29 0xb6e3ea60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#30 0xb6e3f7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#31 0xb6e77847 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#32 0xb75daa72 in ?? () from /usr/lib/libQtNetwork.so.4
#33 0xb75c9ceb in ?? () from /usr/lib/libQtNetwork.so.4
#34 0xb75cb056 in ?? () from /usr/lib/libQtNetwork.so.4
#35 0xb64cd8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#36 0xb64d572e in QApplication::notify () from /usr/lib/libQtGui.so.4
#37 0xb735ffed in KApplication::notify () from /usr/lib/libkdeui.so.5
#38 0xb6e29e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#39 0xb6e5470a in ?? () from /usr/lib/libQtCore.so.4
#40 0xb5c956f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#41 0xb5c98da3 in ?? ()...

[Jonathan Thomas (echidnaman)]

That's a different crash. You should report a separate bug for it.