Bug 160702 - Kopete crash. Suddenly. Periodically
Summary: Kopete crash. Suddenly. Periodically
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: 0.50.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 162057 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-04-11 13:48 UTC by Sergiy Kotenko
Modified: 2008-07-07 05:22 UTC (History)
2 users (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 Sergiy Kotenko 2008-04-11 13:48:40 UTC
Version:           0.50.1 (using KDE 4.0.3)
Installed from:    Ubuntu Packages
Compiler:          gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu Thread model: posix
OS:                Linux

Kopete crashes suddenly and periodically:


(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1249945920 (LWP 20809)]
[New Thread -1289090160 (LWP 20927)]
[New Thread -1297482864 (LWP 20912)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 20809)]

Thread 3 (Thread -1297482864 (LWP 20912)):
#0  0xb661fa74 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#1  0xb6620225 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x080cb700 in ?? ()
#3  0xb2a9f1a8 in ?? ()
#4  0xb65dd541 in pthread_mutex_lock ()
   from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb6620ac5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#6  0xb7ed94a4 in QEventDispatcherGlib::processEvents (this=0x8650b48, 
    flags=@0xb2a9f22c) at kernel/qeventdispatcher_glib.cpp:340
#7  0xb7ead3de in QEventLoop::processEvents (this=0x85893c8, 
    flags=@0xb2a9f264) at kernel/qeventloop.cpp:142
#8  0xb7ead560 in QEventLoop::exec (this=0x85893c8, flags=@0xb2a9f354)
    at kernel/qeventloop.cpp:184
#9  0xb34094fa in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#10 0xb7dfaeb5 in QThreadPrivate::start (arg=0x8aa5e88)
    at thread/qthread_unix.cpp:181
#11 0xb65db46b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#12 0xb67cd6de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1289090160 (LWP 20927)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb65df676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb67da31d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7dfb29d in QWaitCondition::wait (this=0x85c30b8, mutex=0x85c30b4, 
    time=4294967295) at thread/qwaitcondition_unix.cpp:269
#4  0xb655a8ad in QHostInfoAgent::run (this=0x85c30a8) at qhostinfo.cpp:263
#5  0xb7dfaeb5 in QThreadPrivate::start (arg=0x85c30a8)
    at thread/qthread_unix.cpp:181
#6  0xb65db46b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb67cd6de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1249945920 (LWP 20809)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb678ce96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb678cca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7a8fe20 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 FiNeX 2008-04-12 01:03:01 UTC
Hi! Is the crash reproducible in a specific way or did it crash randomly?
Comment 2 Sergiy Kotenko 2008-04-13 15:52:46 UTC
Hi! Yes, kopete crash randomly. And not every day - today can fall down and then three days can work normally. For example today works normally :)
Comment 3 Sergiy Kotenko 2008-04-14 10:04:08 UTC
Hi!
Today it happened again:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1250359616 (LWP 6451)]
[New Thread -1289503856 (LWP 6531)]
[New Thread -1297896560 (LWP 6528)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 6451)]

Thread 3 (Thread -1297896560 (LWP 6528)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb657a676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb677531d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7d9629d in QWaitCondition::wait (this=0x8954978, mutex=0x8954974, 
    time=4294967295) at thread/qwaitcondition_unix.cpp:269
#4  0xb64f58ad in QHostInfoAgent::run (this=0x8954968) at qhostinfo.cpp:263
#5  0xb7d95eb5 in QThreadPrivate::start (arg=0x8954968)
    at thread/qthread_unix.cpp:181
#6  0xb657646b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb67686de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1289503856 (LWP 6531)):
#0  0xb664a014 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0xb7e7735a in QTimerInfoList::getTime (this=0x89f5fc4, t=@0x89f5fe8)
    at kernel/qeventdispatcher_unix.cpp:348
#2  0xb7e775b5 in QTimerInfoList::updateCurrentTime (this=0x89f5fc4)
    at kernel/qeventdispatcher_unix.cpp:292
#3  0xb7e77c9a in QTimerInfoList::timerWait (this=0x89f5fc4, tm=@0xb323b100)
    at kernel/qeventdispatcher_unix.cpp:415
#4  0xb7e74be8 in timerSourcePrepare (source=0x89f5f90, timeout=0xb323b148)
    at kernel/qeventdispatcher_glib.cpp:134
#5  0xb65baa52 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#6  0xb65bb225 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x089f9420 in ?? ()
#8  0xb323b1a8 in ?? ()
#9  0xb6578541 in pthread_mutex_lock ()
   from /lib/tls/i686/cmov/libpthread.so.0
#10 0xb65bbac5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#11 0xb7e744a4 in QEventDispatcherGlib::processEvents (this=0x8708228, 
    flags=@0xb323b22c) at kernel/qeventdispatcher_glib.cpp:340
#12 0xb7e483de in QEventLoop::processEvents (this=0x869cf98, 
    flags=@0xb323b264) at kernel/qeventloop.cpp:142
#13 0xb7e48560 in QEventLoop::exec (this=0x869cf98, flags=@0xb323b354)
    at kernel/qeventloop.cpp:184
#14 0xb33a44fa in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#15 0xb7d95eb5 in QThreadPrivate::start (arg=0x89f5f30)
    at thread/qthread_unix.cpp:181
#16 0xb657646b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#17 0xb67686de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1250359616 (LWP 6451)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6727e96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6727ca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7a2ae20 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 4 Olivier Goffart 2008-04-23 01:18:14 UTC
Which protocol and which plugin are you using?  Can you determine if one of them is responsible?
Comment 5 Sergiy Kotenko 2008-04-23 20:30:09 UTC
Hi! 
I'm use two protocols with kopete: ICQ of and of Jabber. The day before yesterday (Monday, 21.04.2008) I deleted support of Jabber and while works normally (to it fallen ~2 times per a day). 
Also i'm use next plugin:
1) Contact Notes
2) Preview of pictures in chats
3) History
4) Statistics
I hope this information will help you.
Comment 6 Sergiy Kotenko 2008-04-23 20:33:32 UTC
*"I deleted support of Jabber"
excuse me, usually I deleted Jabber account :)
Comment 7 Matt Rogers 2008-07-07 04:04:08 UTC
Not using jabber has probably helped with the crashes since the problem is in QCA, an external library that Kopete uses, and not a problem in Kopete. I suggest submitting this to delta@lists.affinix.com and see what they say. 
Comment 8 Matt Rogers 2008-07-07 05:22:45 UTC
*** Bug 162057 has been marked as a duplicate of this bug. ***