Bug 175890 - kopete crashes when status changes to offline
Summary: kopete crashes when status changes to offline
Status: RESOLVED DUPLICATE of bug 176821
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-11-23 15:25 UTC by S. Burmeister
Modified: 2008-12-14 18:41 UTC (History)
3 users (show)

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 S. Burmeister 2008-11-23 15:25:47 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

If my network connection is lost kopete notifies me about that and if I click OK in that dialogue it crashes.

Same if I change the4 status to offline manually.
Comment 1 S. Burmeister 2008-11-23 15:25:56 UTC
Anwendung: Kopete (kopete), Signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
0x00007f7078d73261 in nanosleep () from /lib64/libc.so.6
[Current thread is 0 (LWP 5078)]

Thread 4 (Thread 0x40ed8950 (LWP 5081)):
#0  0x00007f70761be75a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f70761c2040 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f70761c21dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f707ab8f3ce in QEventDispatcherGlib::processEvents (this=0x845960, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:321
#4  0x00007f707ab65782 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1089306448}) at kernel/qeventloop.cpp:143
#5  0x00007f707ab6590d in QEventLoop::exec (this=0xaec340, flags={i = 1089306848}) at kernel/qeventloop.cpp:194
#6  0x00007f7069b9b0ab in QCA::SyncThread::run () from /usr/lib64/libqca.so.2
#7  0x00007f707aa7e022 in QThreadPrivate::start (arg=0xcbfce0) at thread/qthread_unix.cpp:185
#8  0x00007f707a80a040 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f7078da40cd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x41b40950 (LWP 5082)):
#0  0x00007f707a80ddd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f707aa7efd9 in QWaitCondition::wait (this=0x1212100, mutex=0x12120f8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:82
#2  0x00007f707a5737bc in QHostInfoAgent::run (this=0x12120e0) at kernel/qhostinfo.cpp:241
#3  0x00007f707aa7e022 in QThreadPrivate::start (arg=0x12120e0) at thread/qthread_unix.cpp:185
#4  0x00007f707a80a040 in start_thread () from /lib64/libpthread.so.0
#5  0x00007f7078da40cd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x42b42950 (LWP 5128)):
#0  0x00007f7078d9d662 in select () from /lib64/libc.so.6
#1  0x00007f70695e7afa in posix_timer_do () from /usr/lib64/libortp.so.5
#2  0x00007f70695e87d5 in rtp_scheduler_schedule () from /usr/lib64/libortp.so.5
#3  0x00007f707a80a040 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f7078da40cd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f70804b0700 (LWP 5078)):
[KCrash Handler]
#5  QTimer::stop (this=0x7007f7079025a1c) at kernel/qtimer.cpp:242
#6  0x00007f707a58bdfc in QAbstractSocketPrivate::readFromSocket (this=0x1218020) at socket/qabstractsocket.cpp:989
#7  0x00007f707a58bf77 in QAbstractSocketPrivate::canReadNotification (this=0x1218020) at socket/qabstractsocket.cpp:543
#8  0x00007f707a57cf41 in QReadNotifier::event (this=<value optimized out>, e=0x67b134) at socket/qnativesocketengine.cpp:968
#9  0x00007f707993a17d in QApplicationPrivate::notify_helper (this=0x6a3050, receiver=0xafbc20, e=0x7fff884f9320) at kernel/qapplication.cpp:3803
#10 0x00007f7079941f2a in QApplication::notify (this=0x7fff884f9610, receiver=0xafbc20, e=0x7fff884f9320) at kernel/qapplication.cpp:3768
#11 0x00007f707f31a31b in KApplication::setTopWidget (this=0x7007f7079025a1c, topWidget=0x67b134) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:1122
#12 0x00007fff884f9320 in ?? ()
#13 0x00007fff884f9610 in ?? ()
#14 0x00007f707ab66e81 in QCoreApplication::notifyInternal (this=0x7fff884f9610, receiver=0xafbc20, event=0xafbc20) at kernel/qcoreapplication.cpp:587
#15 0x00007f707ab8f629 in socketNotifierSourceDispatch (source=0x6b4950) at kernel/qcoreapplication.h:209
#16 0x00007f70761be93a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f70761c2040 in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f70761c21dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f707ab8f3af in QEventDispatcherGlib::processEvents (this=0x697370, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319
#20 0x00007f70799caccf in QGuiEventDispatcherGlib::processEvents (this=0x7007f7079025a1c, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198
#21 0x00007f707ab65782 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -2008050368}) at kernel/qeventloop.cpp:143
#22 0x00007f707ab6590d in QEventLoop::exec (this=0x7fff884f9580, flags={i = -2008050288}) at kernel/qeventloop.cpp:194
#23 0x00007f707ab67dfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#24 0x000000000044a36c in main (argc=3, argv=0x7fff884fa3c8) at /home/kde-devel/kde/src/KDE/kdenetwork/kopete/kopete/main.cpp:102

Comment 2 LuRan 2008-11-26 04:51:12 UTC
I have seen this kind of crash too, but for me it only happens with jabber protocol. If I only use my wlm account, I can go on/offline without any trouble. I notices the "CROSS YOUR FINGERS! THIS IS GONNA BE WILD" in the source code. Maybe this is a known crash?
Comment 3 Steffen Schloenvoigt 2008-11-29 10:30:03 UTC
Same here. And yes that seems to happen only if jabber/gtalk is used.
Comment 4 Dario Andres 2008-12-04 19:24:56 UTC
This seems to be related/duplicate to bug 176821 (same backtrace, same description)
Comment 5 Dario Andres 2008-12-14 18:41:18 UTC
Marking as duplicate of bug 176821. If you think this is not a duplicate you can re-open the report. Thanks :)

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