Bug 172922

Summary: The application Kopete (kopete) crashed and caused the signal 11 (SIGSEGV).
Product: [Unmaintained] kopete Reporter: Bernardino <bernardino_rozada>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: crash CC: bernardino_rozada, kojot350, trance202
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bernardino 2008-10-16 08:21:31 UTC
Version:           o.60.2 (using KDE 4.1.2)
Installed from:    Mandriva RPMs

The application Kopete (kopete) crashed and caused the signal 11 (SIGSEGV).
Comment 1 Bernardino 2008-10-16 08:22:17 UTC
The application Kopete (kopete) crashed and caused the signal 11 (SIGSEGV).
Comment 2 Roman Jarosz 2008-10-16 09:22:11 UTC
Please post the backtrace of the crash.
Comment 3 Paweł Prażak 2008-10-16 17:30:44 UTC
How to post backtrace? Read this if in doubt:
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports
Thanks!
Comment 4 Roman Jarosz 2008-10-16 22:05:16 UTC
Btw. did it happen during KDE logout?
Comment 5 Bernardino 2008-10-16 22:24:03 UTC
... Tonight is back to break for no apparent reason
Comment 6 Roman Jarosz 2008-10-17 00:32:41 UTC
Please post the backtrace and tell us what did you do before Kopete crashes
Comment 7 Bernardino 2008-10-17 10:00:51 UTC
I was writing text using another tool. 
 Kopete already in the network when they broke the two 
 times
Comment 8 Roman Jarosz 2008-10-17 10:05:02 UTC
We can't fix it untill you post a backtrace of the crash.
Comment 9 Bernardino 2008-10-17 10:23:53 UTC
  Thank you, this is not a tool that uses a lot, but 
 well almost not use it. Excuse my English because for 
 communicate using the translator of google, as they do not speak 
 that language. I just wanted to cooperate by providing a bug. 
 Greetings
Comment 10 Paweł Prażak 2008-10-17 20:07:19 UTC
Thanks for your good intentions :)
Unfortunately, without proper backtrace, we don't know what went wrong and caused the crash. 
Comment 11 Raphael 2008-10-26 19:36:46 UTC
my kopete crash also on kde-logout. each time, the logout-screen "hang" until I press the power-button to shutdown the system or I kill X.

I'm not sure if this bugreport is the same crash like each logout. KDE 4.1.2 actual on 26.10.08/19:36 from Kubuntu 8.10 (intrepid).

nwendung: Kopete (kopete), Signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
...100 times more...
[Thread debugging using libthread_db enabled]
[New Thread 0x7f22244df6f0 (LWP 6914)]
(no debugging symbols found)
(no debugging symbols found)
...100 times more...
(no debugging symbols found)
[KCrash handler]
#5  0x00007f2220095fd5 in raise () from /lib/libc.so.6
#6  0x00007f2220097b43 in abort () from /lib/libc.so.6
#7  0x00007f22224126b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f22224127fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f2223a6b517 in ?? () from /usr/lib/libkopete.so.4
#10 0x00007f2223a6d507 in Kopete::PluginManager::slotPluginDestroyed ()
   from /usr/lib/libkopete.so.4
#11 0x00007f2223a70b17 in Kopete::PluginManager::qt_metacall ()
   from /usr/lib/libkopete.so.4
#12 0x00007f2222517134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#13 0x00007f22225175a4 in QObject::destroyed () from /usr/lib/libQtCore.so.4
#14 0x00007f22225190ee in QObject::~QObject () from /usr/lib/libQtCore.so.4
#15 0x00007f2223a75b1a in Kopete::Protocol::~Protocol ()
   from /usr/lib/libkopete.so.4
#16 0x00007f220ed23f0e in ?? () from /usr/lib/kde4/kopete_aim.so
#17 0x00007f2223a7204f in ?? () from /usr/lib/libkopete.so.4
#18 0x00007f2223a6b2d7 in ?? () from /usr/lib/libkopete.so.4
#19 0x00007f222009966d in exit () from /lib/libc.so.6
#20 0x00007f222008146d in __libc_start_main () from /lib/libc.so.6
#21 0x00000000004233b9 in _start ()
#0  0x00007f222010b621 in nanosleep () from /lib/libc.so.6
Comment 12 Roman Jarosz 2008-10-26 20:49:18 UTC
Raphael: your crash is duplicate of bug 172011, and it should be fixed in kdenetwork (4:4.1.2-0ubuntu3).

I'm closing this bug because we don't have enough info to fix/reproduce this bug.