kopete segfaults when connecting to ejabberd with shared roster

Bug #273322 reported by Orange Peel Beef
2
Affects Status Importance Assigned to Milestone
KDE Network
New
Undecided
Unassigned
kdenetwork (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: kopete

Crash when connecting to ejabberd with shared rosters in Intrepid Ibex (was working fine with kopete in hardy)

Description: Ubuntu intrepid (development branch)
Release: 8.10

kopete:
  Installed: 4:4.1.1-0ubuntu2

[ 5280.653556] kopete[9878]: segfault at 9223000 ip b649eb11 sp bfb9716c error 6 in libc-2.8.90.so[b6426000+158000]
[ 5458.305970] kopete[10659]: segfault at 8919000 ip b6439b11 sp bfd3339c error 6 in libc-2.8.90.so[b63c1000+158000]
[ 5505.483683] kopete[10708]: segfault at a688000 ip b6441b11 sp bfc3929c error 6 in libc-2.8.90.so[b63c9000+158000]

Revision history for this message
Orange Peel Beef (orangepeelbeef) wrote :

(gdb) bt
#0 0xb64a4b11 in memcpy () from /lib/tls/i686/cmov/libc.so.6
#1 0xb788d070 in KNetwork::Internal::KSocketBuffer::sendTo (this=0x8e464c8, dev=0x8e4a048, len=-1)
    at /usr/include/bits/string3.h:52
#2 0xb7876fd0 in KNetwork::KBufferedSocket::slotWriteActivity (this=0x8e432b8)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349
#3 0xb7876e00 in KNetwork::KBufferedSocket::qt_metacall (this=0x8e432b8, _c=QMetaObject::InvokeMetaMethod, _id=1,
    _a=0xbfa9be7c) at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/kdecore/k3bufferedsocket.moc:68
#4 0xb75e4c00 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#5 0xb75e5982 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#6 0xb761f7d3 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#7 0xb75ea7d7 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#8 0xb6ab3c9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#9 0xb6abbb1e in QApplication::notify () from /usr/lib/libQtGui.so.4
#10 0xb7b0e19d in KApplication::notify (this=0xbfa9c4ac, receiver=0x8f74fe8, event=0xbfa9c240)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#11 0xb75d0001 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#12 0xb75fa8aa in ?? () from /usr/lib/libQtCore.so.4
#13 0xb5fb76f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0xb5fbada3 in ?? () from /usr/lib/libglib-2.0.so.0
#15 0xb5fbaf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#16 0xb75fa618 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#17 0xb6b4e2b5 in ?? () from /usr/lib/libQtGui.so.4
#18 0xb75ce6ca in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#19 0xb75ce88a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#20 0xb75d0f45 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#21 0xb6ab3b17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#22 0x0808aa6f in main (argc=2, argv=0xbfa9c894) at /build/buildd/kdenetwork-4.1.1/kopete/kopete/main.cpp:102

Revision history for this message
Orange Peel Beef (orangepeelbeef) wrote :
Download full text (5.2 KiB)

(gdb) thread apply all backtrace

Thread 5 (Thread 0xb18feb90 (LWP 13820)):
#0 0xb8087430 in __kernel_vsyscall ()
#1 0xb5f72392 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb651f894 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3 0xb74e46ec in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4 0xb7884ca9 in KNetwork::Internal::KResolverManager::requestData (this=0x8646120, th=0x8799780, maxWaitTime=2000)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3resolvermanager.cpp:370
#5 0xb7884d24 in KNetwork::Internal::KResolverThread::run (this=0x8799780)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3resolvermanager.cpp:266
#6 0xb74e36ce in ?? () from /usr/lib/libQtCore.so.4
#7 0xb5f6e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8 0xb651164e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 0xb2af4b90 (LWP 13818)):
#0 0xb8087430 in __kernel_vsyscall ()
#1 0xb5f72392 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb651f894 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3 0xb74e46ec in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4 0xb7884ca9 in KNetwork::Internal::KResolverManager::requestData (this=0x8646120, th=0x87ad1e8, maxWaitTime=2000)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3resolvermanager.cpp:370
#5 0xb7884d24 in KNetwork::Internal::KResolverThread::run (this=0x87ad1e8)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3resolvermanager.cpp:266
#6 0xb74e36ce in ?? () from /usr/lib/libQtCore.so.4
#7 0xb5f6e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8 0xb651164e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb32f5b90 (LWP 13817)):
#0 0xb8087430 in __kernel_vsyscall ()
#1 0xb6506de7 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb5fbec32 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0xb5fbef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#4 0xb75fe618 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#5 0xb75d26ca in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#6 0xb75d288a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#7 0xb35e5e59 in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#8 0xb74e36ce in ?? () from /usr/lib/libQtCore.so.4
#9 0xb5f6e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#10 0xb651164e in clone () from /lib/tls/i686/...

Read more...

Revision history for this message
Harald Sitter (apachelogger) wrote :

This report + backtraces need to be forwarded to http://bugs.kde.org

Changed in kdenetwork:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Orange Peel Beef (orangepeelbeef) wrote :

I noticed that I didn't have the kdenetwork package installed. I installed it and kopete doesn't seem to be segfaulting anymore. If this is the case, shouldn't kdenetwork be a dependency?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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