Bug 171731 - kopete crashed on shutdown
Summary: kopete crashed on shutdown
Status: RESOLVED DUPLICATE of bug 172011
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.60.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 175961 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-27 10:31 UTC by Matthias
Modified: 2008-11-29 21:00 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
A second backtrace (5.65 KB, application/octet-stream)
2008-09-27 10:31 UTC, Matthias
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias 2008-09-27 10:31:07 UTC
Version:           0.60.1 (using KDE 4.1.1)
Compiler:          I'm using the standard ubuntu binary packages 
OS:                Linux
Installed from:    Ubuntu Packages

Initial situation:
I have a running KDE 4.1.1 session with the following applications running in background:
Kopete, Kontact, the Wallet-application and amaroK

Then I start the shutdown procedure from KMenu.

After all plasma objects dissappeared I get a notification that kopete crashed. This does not happen every time. Sometimes kontact crashes also or instead.

The backtrace:
Anwendung: Kopete (kopete), Signal SIGSEGV
(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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7f6d940 (LWP 7273)]
[New Thread 0xb3efdb90 (LWP 7397)]
[New Thread 0xb6043b90 (LWP 7393)]
(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]
#6  0x4d807f67 in ?? () from /usr/lib/kde4/lib/libkopete.so.4
#7  0xb652613d in ?? () from /usr/lib/kde4/lib/kde4/kopete_statistics.so
#8  0xb6527b7d in ?? () from /usr/lib/kde4/lib/kde4/kopete_statistics.so
#9  0xb65198b7 in ?? () from /usr/lib/kde4/lib/kde4/kopete_statistics.so
#10 0x421349ac in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4
#11 0x42135c5c in QObject::event () from /usr/lib/libQtCore.so.4
#12 0x4cbb70dc in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#13 0x4cbbbd39 in QApplication::notify () from /usr/lib/libQtGui.so.4
#14 0x4c3101c3 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#15 0x421260b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#16 0x42127469 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#17 0x4212768d in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#18 0x42127782 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#19 0x4cbb69d7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#20 0x08087efb in ?? ()
#21 0x4303f450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#22 0x080644b1 in _start ()
#
Comment 1 Matthias 2008-09-27 10:31:39 UTC
Created attachment 27588 [details]
A second backtrace
Comment 2 FiNeX 2008-09-28 18:53:20 UTC
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!
Comment 3 Matthias 2008-09-28 19:15:43 UTC
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) :-(
Comment 4 Gianfranco L'Abbate 2008-11-05 17:14:56 UTC
I can confirm this bug
Comment 5 Stefan Katscher 2008-11-08 23:53:22 UTC
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)
Comment 6 Stefan Katscher 2008-11-09 00:30:55 UTC
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 ()
Comment 7 Rob Stewart 2008-11-16 23:50:53 UTC
I too can confirm this. My backtrace is identical to Stefan Katscher's.
Comment 8 Wyatt Best 2008-11-18 19:58:17 UTC
I can confirm this bug.
Comment 9 Jacopo De Simoi 2008-11-22 02:03:14 UTC
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


Comment 10 Davide Castellone 2008-11-24 12:37:28 UTC
I can confirm this bug in Kubuntu 8.10 with KDE 4.1.3.
Comment 11 Oliver Putz 2008-11-29 18:24:26 UTC
*** Bug 175961 has been marked as a duplicate of this bug. ***
Comment 12 Oliver Putz 2008-11-29 18:29:35 UTC
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.
Comment 13 A. Futschik 2008-11-29 20:57:08 UTC
(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
Comment 14 Oliver Putz 2008-11-29 21:00:42 UTC
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 ***