Bug 174374 - kopete crash on kde closing
Summary: kopete crash on kde closing
Status: RESOLVED DUPLICATE of bug 172011
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-05 21:10 UTC by Vincent VIGNOLLE
Modified: 2008-11-06 11:58 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (4.96 KB, text/plain)
2008-11-06 10:58 UTC, Vincent VIGNOLLE
Details
my kopete crash amd64 icq kopete-0.60.3 kde-4.1.3 (1.50 KB, text/plain)
2008-11-06 11:41 UTC, Fritz Heinrichmeyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent VIGNOLLE 2008-11-05 21:10:56 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

Kopete is connected or not
Kopete crash when i close KDE4
An error window was diplaying
Comment 1 Médéric Boquien 2008-11-05 21:29:04 UTC
Hello,

Thank you for your report. Can you please provide the backtrace of the crash? Instructions are provided on this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports .

Thanks.
Comment 2 Fritz Heinrichmeyer 2008-11-06 10:04:15 UTC
same here, but only at home with i386 and DSL-Router, not at work with permanent connection, static ip adress and amd64 box. This happenend again this morning after upgrade to 4.1.3 in ubuntu/intrepid
Comment 3 Fritz Heinrichmeyer 2008-11-06 10:41:30 UTC
now kopete crashes also on logout at the amd64 box with permanent connection, amarok crashes when started from command line but works when started from menu ...but this is another story ...
Comment 4 Vincent VIGNOLLE 2008-11-06 10:58:29 UTC
Created attachment 28356 [details]
backtrace
Comment 5 Roman Jarosz 2008-11-06 11:05:37 UTC
Fritz do you have a backtrace, because Vincent's crash should be fixed in 4.1.3.

Vincent which version of kdenetwork package do you have? It should be fixed in(4:4.1.2-0ubuntu3).

Also don't forget to restart Kopete after the update.
Comment 6 Fritz Heinrichmeyer 2008-11-06 11:41:37 UTC
Created attachment 28358 [details]
my kopete crash amd64 icq kopete-0.60.3 kde-4.1.3
Comment 7 Fritz Heinrichmeyer 2008-11-06 11:42:20 UTC
created attachment http://bugs.kde.org/attachment.cgi?id=28358
Comment 8 Christophe Marin 2008-11-06 11:54:30 UTC
copy/paste : 

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 0x7fcfec30e6f0 (LWP 11673)]
[KCrash handler]
#5  0x00007fcfe7ec5fd5 in raise () from /lib/libc.so.6
#6  0x00007fcfe7ec7b43 in abort () from /lib/libc.so.6
#7  0x00007fcfea2426b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007fcfea2427fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007fcfeb89cf17 in ?? () from /usr/lib/libkopete.so.4
#10 0x00007fcfeb89ef07 in Kopete::PluginManager::slotPluginDestroyed ()
   from /usr/lib/libkopete.so.4
#11 0x00007fcfeb8a25a7 in Kopete::PluginManager::qt_metacall ()
   from /usr/lib/libkopete.so.4
#12 0x00007fcfea347134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#13 0x00007fcfea3475a4 in QObject::destroyed () from /usr/lib/libQtCore.so.4
#14 0x00007fcfea3490ee in QObject::~QObject () from /usr/lib/libQtCore.so.4
#15 0x00007fcfeb8a75aa in Kopete::Protocol::~Protocol ()
   from /usr/lib/libkopete.so.4
#16 0x00007fcfd855bae7 in ?? () from /usr/lib/kde4/kopete_icq.so
#17 0x00007fcfeb8a3adf in ?? () from /usr/lib/libkopete.so.4
#18 0x00007fcfeb89ccd7 in ?? () from /usr/lib/libkopete.so.4
#19 0x00007fcfe7ec966d in exit () from /lib/libc.so.6
#20 0x00007fcfe7eb146d in __libc_start_main () from /lib/libc.so.6
#21 0x00000000004233b9 in _start ()
#0  0x00007fcfe7f3b621 in nanosleep () from /lib/libc.so.6
Comment 9 Christophe Marin 2008-11-06 11:58:15 UTC

*** This bug has been marked as a duplicate of bug 172011 ***