Bug 161937 - Kopete crashes when using jabber protocol
Summary: Kopete crashes when using jabber protocol
Status: RESOLVED DUPLICATE of bug 157686
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-11 09:12 UTC by Hans-Peter Schadler
Modified: 2008-07-03 16:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Schadler 2008-05-11 09:12:55 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) 
OS:                Linux

Kopete crashes if i try to login to a openfire jabber server. I am using MSN and ICQ transports. This happens since the Kopete version that shipped with KDE 4.0.0 and still happens with recent KDE svn revisions (freshly compiled yesterday).

Backtrace:

Application: Kopete (kopete), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7f52b61f1780 (LWP 20327)]
[KCrash handler]
#5  0x00007f52ad57b09c in memcpy () from /lib/libc.so.6
#6  0x00007f52b570950e in KNetwork::Internal::KSocketBuffer::sendTo ()
   from /home/hps/kde/kde4/lib/libkdecore.so.5
#7  0x00007f52b56f9299 in KNetwork::KBufferedSocket::slotWriteActivity ()
   from /home/hps/kde/kde4/lib/libkdecore.so.5
#8  0x00007f52b56f8422 in KNetwork::KBufferedSocket::qt_metacall ()
   from /home/hps/kde/kde4/lib/libkdecore.so.5
#9  0x00007f52b5d47b3b in QMetaObject::activate (sender=0xdd3d40, 
    from_signal_index=<value optimized out>, to_signal_index=4, 
    argv=0x1fffffffffff677) at kernel/qobject.cpp:3007
#10 0x00007f52b5d7bbae in QSocketNotifier::activated (this=0xdbe29e, _t1=40)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#11 0x00007f52b5d4f8ef in QSocketNotifier::event (this=0xdd3d40, 
    e=0x7fffbe228dc0) at kernel/qsocketnotifier.cpp:326
#12 0x00007f52b3c0d9ff in QApplicationPrivate::notify_helper (this=0x6a2270, 
    receiver=0xdd3d40, e=0x7fffbe228dc0) at kernel/qapplication.cpp:3772
#13 0x00007f52b3c14bc5 in QApplication::notify (this=0x7fffbe2290a0, 
    receiver=0xdd3d40, e=0x7fffbe228dc0) at kernel/qapplication.cpp:3739
#14 0x00007f52b4b1ab6b in KApplication::notify ()
   from /home/hps/kde/kde4/lib/libkdeui.so.5
#15 0x00007f52b5d38284 in QCoreApplication::notifyInternal (
    this=0x7fffbe2290a0, receiver=0xdd3d40, event=0x7fffbe228dc0)
    at kernel/qcoreapplication.cpp:583
#16 0x00007f52b5d5c51a in socketNotifierSourceDispatch (source=0x6a55d0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#17 0x00007f52ace68262 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#18 0x00007f52ace6b516 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x00007f52ace6b9af in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#20 0x00007f52b5d5c67f in QEventDispatcherGlib::processEvents (this=0x68e280, 
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325
#21 0x00007f52b3c88e3f in QGuiEventDispatcherGlib::processEvents (
    this=0xdbe29e, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007f52b5d37675 in QEventLoop::processEvents (
    this=<value optimized out>, flags=@0x7fffbe228fd0)
    at kernel/qeventloop.cpp:149
#23 0x00007f52b5d377e7 in QEventLoop::exec (this=0x7fffbe229010, 
    flags=@0x7fffbe229020) at kernel/qeventloop.cpp:196
#24 0x00007f52b5d397f1 in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:845
#25 0x0000000000446394 in main ()
#0  0x00007f52ad59bb81 in nanosleep () from /lib/libc.so.6
Comment 1 Christophe Marin 2008-07-03 16:39:08 UTC

*** This bug has been marked as a duplicate of 157686 ***