Bug 158972 - kopete krashed on quit
Summary: kopete krashed on quit
Status: RESOLVED DUPLICATE of bug 172011
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:
Depends on:
Blocks:
 
Reported: 2008-03-08 17:37 UTC by Sergiy Kotenko
Modified: 2008-10-28 09:53 UTC (History)
4 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-03-08 17:37:07 UTC
Version:           0.50.1 (using KDE 4.0.2)
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
OS:                Linux

When quit from kopete (Ctrl+q) or logout from KDE kopete krashed.
Comment 1 Sergiy Kotenko 2008-03-08 17:37:48 UTC
trace:
(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 -1249741120 (LWP 6428)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (process 6428)]

Thread 1 (Thread -1249741120 (LWP 6428)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb67bde96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb67bdca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7abf640 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 2 Sergiy Kotenko 2008-03-12 16:09:55 UTC
Today kopete crash 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 -1250281792 (LWP 6361)]
[New Thread -1325474928 (LWP 6401)]
[New Thread -1291879536 (LWP 6397)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 6361)]

Thread 3 (Thread -1291879536 (LWP 6397)):
#0  0xb658b968 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#1  0xb6787526 in pthread_mutex_unlock () from /lib/tls/i686/cmov/libc.so.6
#2  0xb65cca46 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#3  0xb65cd225 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x08937810 in ?? ()
#5  0xb2ff71a8 in ?? ()
#6  0xb658a541 in pthread_mutex_lock ()
   from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb65cdac5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#8  0xb7e854a4 in QEventDispatcherGlib::processEvents (this=0x8611d58, 
    flags=@0xb2ff722c) at kernel/qeventdispatcher_glib.cpp:340
#9  0xb7e593de in QEventLoop::processEvents (this=0x8618280, 
    flags=@0xb2ff7264) at kernel/qeventloop.cpp:142
#10 0xb7e59560 in QEventLoop::exec (this=0x8618280, flags=@0xb2ff7354)
    at kernel/qeventloop.cpp:184
#11 0xb33904fa in QCA::SyncThread::run () from /usr/lib/libqca.so.2
#12 0xb7da6eb5 in QThreadPrivate::start (arg=0x88f7230)
    at thread/qthread_unix.cpp:181
#13 0xb658846b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#14 0xb677a6de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread -1325474928 (LWP 6401)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb658c676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb678731d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7da729d in QWaitCondition::wait (this=0x8957548, mutex=0x8957544, 
    time=4294967295) at thread/qwaitcondition_unix.cpp:269
#4  0xb65078ad in QHostInfoAgent::run (this=0x8957538) at qhostinfo.cpp:263
#5  0xb7da6eb5 in QThreadPrivate::start (arg=0x8957538)
    at thread/qthread_unix.cpp:181
#6  0xb658846b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb677a6de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1250281792 (LWP 6361)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6739e96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6739ca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7a3b640 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 3 Leticia Hernández 2008-07-06 14:02:07 UTC
I can't reproduce this crash.  Has it occurred again since you reported this bug? 
Comment 4 A. Spehr 2008-07-07 00:29:28 UTC
Also, what were you doing when you got it? Anything odd? What service were you using?

If you install kubuntu's debug packages, this backtrace will be useful:
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports

That's the most helpful thing you can do for this.
Thanks!
Comment 5 Michael Höller 2008-10-06 08:45:26 UTC
Hello, 
I have the same problem on openSuSE 11.0 (latest update) with KDE 4.1.2 pakages from the Factory:Desktop rep.
The crash happens every time when I logoff the KDE session and kopete is quit implicitly. Unfortunately the crash stopps the KDE shutdown so that is seems to hang on a black screen. STRG-ALT-BACKSPC twice restarts the x sever and an system shutdown can be continued.

Please let me know which data I should collet to provide helpfull informetion.

Best regards 
Michael
Comment 6 Nicolas L. 2008-10-23 07:34:58 UTC
can it be a duplicate of bug http://bugs.kde.org/172011 ?
Comment 7 Oliver Putz 2008-10-27 21:13:08 UTC
Jep, from the description it definitively is another duplicate of bug #172011, so I'll mark it as one. However, as the backtrace in comment #2 seems to differ from the initial problem described in this bug: Sergiy, if you encounter such a crash with KDE-4.1.3 or later, please file a new bugreport.

*** This bug has been marked as a duplicate of bug 172011 ***
Comment 8 Oliver Putz 2008-10-27 21:24:51 UTC
Addendum: The backtrace in question from comment #2 to me looks like a duplicate of bug #171509 (which should be fixed in KDE-4.1.70)
Comment 9 Sergiy Kotenko 2008-10-28 09:53:25 UTC
Hello!
When I used kubuntu 8.04 (and 8.0.4.1), everything was good, this bug does not reproduced.
But in kubuntu 8.10 (KDE 4.1.2) mistake is repeated again...
I will wait for the release of KDE 4.1.3 in kubuntu, and if the error repeated again - make a new bugreport.
Thanx.