| Summary: | kopete crashed on shutdown | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Matthias <m.deege> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | adrien.futschik, dc.kastel, finex, jacopods+kde, jeawithlove, Regnaron, skatscher, wyattbest |
| Priority: | NOR | ||
| Version: | 0.60.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | A second backtrace | ||
|
Description
Matthias
2008-09-27 10:31:07 UTC
Created attachment 27588 [details]
A second backtrace
Hi Matthias, please follow the instruction on this website for provide an useful backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Thanks a lot! Hi FiNeX, thanks for the information. At the moment, Ubuntu unfortunately does not seem to offer any dbg-packages for kopete (at least I don't see them in aptitude) :-( I can confirm this bug I can confirm this bug, too. It seems to appear only on shutdown, if Kopete is in offline state. I use Kopete with an ICQ account. (Kopete 0.60.3) This is my backtrace: Anwendung: Kopete (kopete), Signal SIGABRT (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb588e6c0 (LWP 5616)] [KCrash handler] #6 0xb7fda430 in __kernel_vsyscall () #7 0xb6389880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb638b248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb740d795 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb740d872 in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb7f3327c in ?? () from /usr/lib/libkopete.so.4 #12 0xb7f353db in Kopete::PluginManager::slotPluginDestroyed () from /usr/lib/libkopete.so.4 #13 0xb7f38c6f in Kopete::PluginManager::qt_metacall () from /usr/lib/libkopete.so.4 #14 0xb751aa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb751ae60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb751aeeb in QObject::destroyed () from /usr/lib/libQtCore.so.4 #17 0xb751c9a9 in QObject::~QObject () from /usr/lib/libQtCore.so.4 #18 0xb7f328ad in Kopete::Plugin::~Plugin () from /usr/lib/libkopete.so.4 #19 0xb7f3e3b2 in Kopete::Protocol::~Protocol () from /usr/lib/libkopete.so.4 #20 0xb357fd47 in OscarProtocol::~OscarProtocol () from /usr/lib/libkopete_oscar.so.4 #21 0xb36262bb in ?? () from /usr/lib/kde4/kopete_icq.so #22 0xb7f3a252 in ?? () from /usr/lib/libkopete.so.4 #23 0xb7f3302a in ?? () from /usr/lib/libkopete.so.4 #24 0xb7eae74b in ?? () from /usr/lib/libkopete.so.4 #25 0xb638cd69 in exit () from /lib/tls/i686/cmov/libc.so.6 #26 0xb637468d in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #27 0x08063d61 in _start () #0 0xb7fda430 in __kernel_vsyscall () I too can confirm this. My backtrace is identical to Stefan Katscher's. I can confirm this bug. I can confirm it is still present in 4.1.3: kopete crashes on logout but for me it happens only when it is docked in the systray; no crash occurs if kopete is either minimized or shown. Can anyone confirm this behaviour?
Here is the my backtrace, it looks quite similar to Stefan's indeed
Application: Kopete (kopete), signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1aa72f5700 (LWP 23896)]
[KCrash handler]
#5 0x00007f1a9df923c5 in raise () from /lib64/libc.so.6
#6 0x00007f1a9df9373e in abort () from /lib64/libc.so.6
#7 0x00007f1aa6d4d795 in qt_message_output ()
from /usr/lib64/qt4/libQtCore.so.4
#8 0x00007f1aa6d4d8c7 in qFatal () from /usr/lib64/qt4/libQtCore.so.4
#9 0x00007f1aa472876b in operator-> (this=0x7f1aa4989a78)
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete-4.1.3/kopete/libkopete/kopetepluginmanager.cpp:98
#10 0x00007f1aa4728c5c in Kopete::PluginManager::slotPluginDestroyed (
this=0x6bcd98, plugin=0x5d58)
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete-4.1.3/kopete/libkopete/kopetepluginmanager.cpp:416
#11 0x00007f1aa472a121 in Kopete::PluginManager::qt_metacall (this=0x6bcd98,
_c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffaf335500)
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete_build/kopete/libkopete/kopetepluginmanager.moc:103
#12 0x00007f1aa6e472bc in QMetaObject::activate ()
from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007f1aa6e47794 in QObject::destroyed ()
from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007f1aa6e47dcc in QObject::~QObject ()
from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007f1aa472f51a in ~Protocol (this=0x8bbda0)
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete-4.1.3/kopete/libkopete/kopeteprotocol.cpp:76
#16 0x00007f1a956ef430 in ~JabberProtocol (this=0x8bbda0)
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete-4.1.3/kopete/protocols/jabber/jabberprotocol.cpp:146
#17 0x00007f1aa472c66c in ~PluginManagerPrivate (this=0x6bcd70)
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete-4.1.3/kopete/libkopete/kopetepluginmanager.cpp:72
#18 0x00007f1aa4728612 in destroy ()
at /var/tmp/portage/kde-base/kopete-4.1.3/work/kopete-4.1.3/kopete/libkopete/kopetepluginmanager.cpp:98
#19 0x00007f1a9df949e9 in exit () from /lib64/libc.so.6
#20 0x00007f1a9df7fb7b in __libc_start_main () from /lib64/libc.so.6
#21 0x0000000000425569 in _start ()
#0 0x00007f1a9dff47b0 in nanosleep () from /lib64/libc.so.6
I can confirm this bug in Kubuntu 8.10 with KDE 4.1.3. *** Bug 175961 has been marked as a duplicate of this bug. *** Just for the record: This one looks like bug #172011 which had a fix that was then later reverted again while the report was closed FIXED anyway. (In reply to comment #12) > Just for the record: This one looks like bug #172011 which had a fix that was > then later reverted again while the report was closed FIXED anyway. > I still have the same bug on KDE 4.1.3 Fedora 10 I think this bug is indeed the same as bug #172011. The real fix there was not applied until 2008-11-08 which was *after* KDE-4.1.3 came out. So this problem should be fixed with KDE-4.1.4. Please feel free to reopen if the problem still exists in KDE-4.1.4 (or KDE-4.2 Beta1) *** This bug has been marked as a duplicate of bug 172011 *** |