kopete crashes when logging in with msn http method

Bug #298999 reported by Miguel Tadeu
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Intrepid by neel
Nominated for Jaunty by fedsotto

Bug Description

Binary package hint: kopete

I'm trying to configure my msn account to use the http method. I'm not configuring the port, just setting it to use the http method. When I try to connect, kopete crashes, leaving this report:

Application: Kopete (kopete), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb57e06c0 (LWP 14890)]
[KCrash handler]
#6 0xb7f35410 in __kernel_vsyscall ()
#7 0xb62db880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb62dd248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb735f795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb735f872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb735f915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb2eeed5a in MSNSocket::WebResponse::WebResponse ()
   from /usr/lib/libkopete_msn_shared.so.4
#13 0xb2ef1a54 in MSNSocket::slotDataReceived ()
   from /usr/lib/libkopete_msn_shared.so.4
#14 0xb2ef2de1 in MSNSocket::qt_metacall ()
   from /usr/lib/libkopete_msn_shared.so.4
#15 0xb2f0859a in ?? () from /usr/lib/libkopete_msn_shared.so.4
#16 0xb746ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb746d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb74a5847 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#19 0xb7692076 in KNetwork::KClientSocketBase::slotReadActivity (this=0x6)
    at /build/buildd/kde4libs-4.1.3/kdecore/network/k3clientsocketbase.cpp:397
#20 0xb76906db in KNetwork::KBufferedSocket::slotReadActivity (this=0x84568a0)
    at /build/buildd/kde4libs-4.1.3/kdecore/network/k3bufferedsocket.cpp:330
#21 0xb76901a6 in KNetwork::KBufferedSocket::qt_metacall (this=0x84568a0,
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf81d13c)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kdecore/k3bufferedsocket.moc:67
#22 0xb746ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb746d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb74a7633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#25 0xb7472637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#26 0xb69398ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#27 0xb694176e in QApplication::notify () from /usr/lib/libQtGui.so.4
#28 0xb7997b2d in KApplication::notify (this=0xbf81d76c, receiver=0x829d3a0,
    event=0xbf81d500)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#29 0xb7457e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#30 0xb748270a in ?? () from /usr/lib/libQtCore.so.4
#31 0xb5e396f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5e3cda3 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb5e3cf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb7482478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb69d3ee5 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb745652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb74566ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#38 0xb7458da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#39 0xb6939767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#40 0x0808aa6f in _start ()
#0 0xb7f35410 in __kernel_vsyscall ()

Revision history for this message
Miguel Tadeu (mtadeunet) wrote :

BTW, on the command line I get this:

kopete(14890) KLocalePrivate::initEncoding: Cannot resolve system encoding, defaulting to ISO 8859-1.
kopete(14890) Kopete::IdentityManager::load: Created identity "q3xzvpirPQ"
miguel@esp-mmota:~$ ASSERT: "i >= 0 && i < size()" in file /usr/include/qt4/QtCore/qbytearray.h, line 379
KCrash: Application 'kopete' crashing...

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you install kdenetwork-dbg and get another backtrace? The current one is missing some lines due to missing debugging symbols. Thanks.

Changed in kopete:
status: New → Incomplete
Miguel Tadeu (mtadeunet)
Changed in kdenetwork:
status: Incomplete → New
Revision history for this message
Miguel Tadeu (mtadeunet) wrote :
Download full text (3.5 KiB)

But of course...here it is...BTW, this happens on i386 and AMD64 versions and happens all the time.

Application: Kopete (kopete), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb58166c0 (LWP 12905)]
[KCrash handler]
#6 0xb7f6c410 in __kernel_vsyscall ()
#7 0xb6311880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb6313248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7395795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7395872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7395915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb2f2cd5a in WebResponse (this=0xbfb07020, bytes=@0xbfb070d4)
    at /usr/include/qt4/QtCore/qbytearray.h:379
#13 0xb2f2fa54 in MSNSocket::slotDataReceived (this=0x85906c8)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/msn/msnsocket.cpp:306
#14 0xb2f30de1 in MSNSocket::qt_metacall (this=0x85906c8,
    _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfb07218)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/msn/msnsocket.moc:118
#15 0xb2f4659a in MSNNotifySocket::qt_metacall (this=0x85906c8,
    _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0xbfb07218)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/msn/msnnotifysocket.moc:105
#16 0xb74a2a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb74a37e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb74db847 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#19 0xb76c8076 in KNetwork::KClientSocketBase::slotReadActivity (this=0x6)
    at /build/buildd/kde4libs-4.1.3/kdecore/network/k3clientsocketbase.cpp:397
#20 0xb76c66db in KNetwork::KBufferedSocket::slotReadActivity (this=0x81cdae8)
    at /build/buildd/kde4libs-4.1.3/kdecore/network/k3bufferedsocket.cpp:330
#21 0xb76c61a6 in KNetwork::KBufferedSocket::qt_metacall (this=0x81cdae8,
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfb0738c)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kdecore/k3bufferedsocket.moc:67
#22 0xb74a2a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb74a37e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb74dd633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#25 0xb74a8637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#26 0xb696f8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#27 0xb697776e in QApplication::notify () from /usr/lib/libQtGui.so.4
#28 0xb79cdb2d in KApplication::notify (this=0xbfb079bc, receiver=0x85453a8,
    event=0xbfb07750)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#29 0xb748de61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#30 0xb74b870a in ?? () from /usr/lib/libQtCore.so.4
#31 0xb5e6f6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5e72da3 in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb5e72f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb74b8478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb6a09ee5 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb748c52a in QEventLoop::processEvents () from /u...

Read more...

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Confirming due to duplicate.

Changed in kdenetwork:
status: New → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This should be fixed in KDE 4.2, as the MSN plugin got a complete rewrite.

Changed in kdenetwork:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.