Bug 250569 - Kopete crashes after trying to connect to IM server
Summary: Kopete crashes after trying to connect to IM server
Status: RESOLVED DUPLICATE of bug 243653
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-08 15:41 UTC by Anderson
Modified: 2011-05-15 12:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anderson 2010-09-08 15:41:58 UTC
Application: kopete (1.0.80)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-20-generic x86_64
Distribution: Ubuntu maverick (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Kopete crashes after trying to connect to IM server and showing some error connection messages.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[Current thread is 1 (Thread 0x7faa4af0d760 (LWP 2633))]

Thread 3 (Thread 0x7faa28f4d710 (LWP 2739)):
#0  0x00007faa41509e71 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#1  0x00007faa4150a318 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007faa4150a8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007faa489d91e6 in QEventDispatcherGlib::processEvents (this=0x1744bf0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007faa489aba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007faa489abdec in QEventLoop::exec (this=0x189b310, flags=) at kernel/qeventloop.cpp:201
#6  0x00007faa313c5565 in ?? () from /usr/lib/kde4/kopete_jabber.so
#7  0x00007faa488b927e in QThreadPrivate::start (arg=0x7faa2c034670) at thread/qthread_unix.cpp:266
#8  0x00007faa46606971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#9  0x00007faa4733f92d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7faa2a3a2710 (LWP 5307)):
#0  0x00007faa473331e3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007faa4150a4a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007faa4150a8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007faa489d91e6 in QEventDispatcherGlib::processEvents (this=0x19b8fb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007faa489aba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007faa489abdec in QEventLoop::exec (this=0x7faa2a3a1db0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007faa488b62fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007faa4898b5f8 in QInotifyFileSystemWatcherEngine::run (this=0x1b5ebc0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007faa488b927e in QThreadPrivate::start (arg=0x1b5ebc0) at thread/qthread_unix.cpp:266
#9  0x00007faa46606971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007faa4733f92d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7faa4af0d760 (LWP 2633)):
[KCrash Handler]
#6  0x0000000001cff23a in ?? ()
#7  0x00007faa493260b4 in KDialogQueue::Private::slotShowQueuedDialog (this=0x1d815a0) at ../../kdeui/dialogs/kdialog.cpp:1087
#8  0x00007faa49326131 in KDialogQueue::qt_metacall (this=0x1ea8fc0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at ./kdialogqueue_p.moc:72
#9  0x00007faa489bebde in QObject::event (this=0x1ea8fc0, e=0x1c51df0) at kernel/qobject.cpp:1219
#10 0x00007faa47a9a04c in QApplicationPrivate::notify_helper (this=0x1339360, receiver=0x1ea8fc0, e=0x1d7b540) at kernel/qapplication.cpp:4396
#11 0x00007faa47a9fb5d in QApplication::notify (this=0x7fff28ad58a0, receiver=0x1ea8fc0, e=0x1d7b540) at kernel/qapplication.cpp:4277
#12 0x00007faa493ccf16 in KApplication::notify (this=0x7fff28ad58a0, receiver=0x1ea8fc0, event=0x1d7b540) at ../../kdeui/kernel/kapplication.cpp:310
#13 0x00007faa489accdc in QCoreApplication::notifyInternal (this=0x7fff28ad58a0, receiver=0x1ea8fc0, event=0x1d7b540) at kernel/qcoreapplication.cpp:732
#14 0x00007faa489afc22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1304bd0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1304bd0) at kernel/qcoreapplication.cpp:1373
#16 0x00007faa489d9653 in sendPostedEvents (s=0x133cb20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#17 postEventSourceDispatch (s=0x133cb20) at kernel/qeventdispatcher_glib.cpp:277
#18 0x00007faa415067e2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007faa4150a748 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007faa4150a8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x00007faa489d9193 in QEventDispatcherGlib::processEvents (this=0x1304320, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#22 0x00007faa47b4c85e in QGuiEventDispatcherGlib::processEvents (this=0x1c51df0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007faa489aba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007faa489abdec in QEventLoop::exec (this=0x7fff28ad57f0, flags=) at kernel/qeventloop.cpp:201
#25 0x00007faa489afebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#26 0x0000000000414432 in _start ()

Possible duplicates by query: bug 249674, bug 248514, bug 244034, bug 243653, bug 221411.

Reported using DrKonqi
Comment 1 Dario Andres 2010-11-20 17:53:42 UTC
[Comment from a bug triager]
The crash information looks related to the one in bug 243653, (but the situation is different). However, the main root cause of the crash may be the same.
Regards
Comment 2 Christoph Feck 2011-05-15 12:38:41 UTC

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