Version: (using KDE 4.1.3) Compiler: 4.3.2 OS: Linux Installed from: Unspecified Linux In an attempt to log into a Gtalk Jabber account, Kopete crashed with the following backtrace. I've compiled all of KDE from source for debugging with the exception of kdepim and qt4. If you need the debugging output for those just ask and I'll recompile those parts as well. I'm running Arch Linux. Application: Kopete (kopete), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb5b6f700 (LWP 6568)] [New Thread 0xb2fd4b90 (LWP 6613)] [KCrash handler] #6 0xb61372b1 in memcpy () from /lib/libc.so.6 #7 0xb7d89340 in KNetwork::Internal::KSocketBuffer::sendTo (this=0x98f0cf0, dev=0x9239e98, len=-1) at /home/daniel/abs/kdelibs/src/kdelibs-4.1.3/kdecore/network/k3socketbuffer.cpp:256 #8 0xb7d73240 in KNetwork::KBufferedSocket::slotWriteActivity ( this=0x983dd60) at /home/daniel/abs/kdelibs/src/kdelibs-4.1.3/kdecore/network/k3bufferedsocket.cpp:349 #9 0xb7d73070 in KNetwork::KBufferedSocket::qt_metacall (this=0x983dd60, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfc5822c) at /home/daniel/abs/kdelibs/src/build/kdecore/k3bufferedsocket.moc:68 #10 0xb7fb082b in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7fb0d82 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb7fe6da3 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4 #13 0xb7fb7187 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4 #14 0xb645eb1c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #15 0xb6464f1e in QApplication::notify () from /usr/lib/libQtGui.so.4 #16 0xb79ca47d in KApplication::notify (this=0xbfc5882c, receiver=0x98a02a0, event=0xbfc585d0) at /home/daniel/abs/kdelibs/src/kdelibs-4.1.3/kdeui/kernel/kapplication.cpp:311 #17 0xb7f9efd1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #18 0xb7fc58e7 in ?? () from /usr/lib/libQtCore.so.4 #19 0xbfc5882c in ?? () #20 0x098a02a0 in ?? () #21 0xbfc585d0 in ?? () #22 0x00000000 in ?? () #0 0xb803e424 in __kernel_vsyscall ()
It should also be added that this doesn't happen when connecting to an MSN account. Only a Jabber (Gtalk) one.
This seems to be a duplicate of bug 170376 ( similar backtrace, crash when using jabber/gtalk)
*** This bug has been marked as a duplicate of bug 170376 ***