Bug 162647 - Kopete crashes on exit
Summary: Kopete crashes on exit
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: 0.50.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 165858 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-05-26 14:49 UTC by Michal Klich
Modified: 2009-02-21 14:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kopete crash log (2.56 KB, application/octet-stream)
2008-07-15 00:27 UTC, Michal Klich
Details
gdb kopete (3.38 KB, text/plain)
2008-07-15 00:28 UTC, Michal Klich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Klich 2008-05-26 14:49:18 UTC
Version:            (using KDE 4.0.4)
Installed from:    Fedora RPMs

Kopete crashes when exiting.
Qt: 4.3.4
KDE: 4.0.4 (KDE 4.0.4)
Kopete: 0.50.1


Plugins enabled: History

Protocols: ICQ, two jabber accounts

Crash log:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7ff83bd997b0 (LWP 2718)]
[New Thread 0x4200a950 (LWP 2762)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00000000011c490a in ?? ()
#6  0x00007ff83585c821 in ?? () from /usr/lib64/kde4/kopete_jabber.so
#7  0x00000035a46fa7d3 in QObject::event () from /usr/lib64/libQtCore.so.4
#8  0x00000035a6990df1 in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#9  0x00000035a699759f in QApplication::notify ()
   from /usr/lib64/libQtGui.so.4
#10 0x00000032b97e3a0b in KApplication::notify ()
   from /usr/lib64/libkdeui.so.5
#11 0x00000035a46ea9f0 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#12 0x00000035a46ec8c3 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#13 0x00000035a470aa6c in ?? () from /usr/lib64/libQtCore.so.4
#14 0x000000359da3749b in g_main_context_dispatch ()
   from /lib64/libglib-2.0.so.0
#15 0x000000359da3ac7d in ?? () from /lib64/libglib-2.0.so.0
#16 0x000000359da3ae3b in g_main_context_iteration ()
   from /lib64/libglib-2.0.so.0
#17 0x00000035a470a741 in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/libQtCore.so.4
#18 0x00000035a6a0647f in ?? () from /usr/lib64/libQtGui.so.4
#19 0x00000035a46e98a8 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#20 0x00000035a46e9a85 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#21 0x00000035a46ecbc7 in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#22 0x0000000000445bcc in _start ()
#0  0x000000359a6a6251 in nanosleep () from /lib64/libc.so.6
Comment 1 Matt Rogers 2008-07-07 05:34:11 UTC
This stacktrace doesn't tell us much exact that the crash is in the Jabber protocol. Please read http://fedoraproject.org/wiki/StackTraces and http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to help us get better information to fix the bug faster. Thanks!
Comment 2 Michal Klich 2008-07-15 00:27:56 UTC
Created attachment 26133 [details]
kopete crash log
Comment 3 Michal Klich 2008-07-15 00:28:14 UTC
Created attachment 26134 [details]
gdb kopete
Comment 4 Michal Klich 2008-07-15 00:28:53 UTC
Please find two attached files. I hope they are useful.
Comment 5 Dominik Tritscher 2008-07-22 19:22:10 UTC
*** Bug 165858 has been marked as a duplicate of this bug. ***
Comment 6 Nicolas L. 2008-10-29 21:45:38 UTC
can you still reproduce with kde 4.1.2 or the kde 4 from your distribution ?
Comment 7 Michal Klich 2008-10-31 00:47:11 UTC
Yes i can reproduce that error. It gets even worse. Now i am not able to close kopete in tray, i can not log back in when i logged out and it still crashes on exit. Though i can not exit kopete, because it still shows in tray, but when i do not login to kopete after fresh reboot and close kopete it crashes.

If you need any info like crash-log please let me know. 

Qt: 4.4.3
KDE: 4.1.2 (KDE 4.1.2)
Kopete: 0.60.2
Comment 8 Nicolas L. 2008-11-09 23:34:24 UTC
can be fixed by commit : http://websvn.kde.org/?view=rev&revision=881699
Comment 9 sagattarii 2008-11-11 10:38:37 UTC
I can confirm this Bug too
Comment 10 Dario Andres 2008-12-06 02:30:16 UTC
This may be related/duplicate of bug 167831
Comment 11 Alan Jones 2008-12-29 09:49:51 UTC
Hi All,

Thanks for the report. Could somebody with this bug confirm it still exists and provide a backtrace with debug symbols? Even if done with the same version as originally this will still assist in confirming if it's a dupe as suspected or a different bug.

Cheers,

Alan.
Comment 12 Dario Andres 2009-02-21 14:23:20 UTC
No news from the bug reporter, marking as WORKSFORME. Please reopen this bug report if you experience the same bug again.