Bug 164593 - kopete crash with signal SIGSEGV when start a ICQ chat (other protocols configured too)
Summary: kopete crash with signal SIGSEGV when start a ICQ chat (other protocols confi...
Status: RESOLVED REMIND
Alias: None
Product: kopete
Classification: Applications
Component: ICQ and AIM Plugins (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-21 14:36 UTC by Ale Hamann
Modified: 2009-02-21 14:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ale Hamann 2008-06-21 14:36:48 UTC
Version:            (using KDE 4.0.80)
Installed from:    Ubuntu Packages
OS:                Linux

I have Kopete configure with too many accounts and different protocols, such as ICQ, AIM, MSN, Jabber, Yahoo...
When I start Kopete, the accounts login automatically (the passwords of each account are stored in a KDE wallet).
But, when I received a IM from ICQ (i thing that maybe is a offline message), Kopete crash.
Another problem is that when i write a message and i try to send it to another ICQ online user, Kopete closes itself without any crash message.

Maybe, this bug can be the same (or similar almost) to the Bug 161208: http://bugs.kde.org/show_bug.cgi?id=161208
But I not sure.

I haven't the kopete-kde4-dbg or any debug symbols for the kopete package (don't exist a package of kopete debug symbols in ubuntu). But, in anyway, the Backtrace is this:

Application: Kopete (kopete), signal SIGSEGV
(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 0x7fe00d195780 (LWP 22678)]
[New Thread 0x42171950 (LWP 22686)]
[New Thread 0x43173950 (LWP 22685)]
[KCrash handler]
#5  0x00007fdff66765b0 in ?? () from /usr/lib/kde4/lib/kde4/kopete_history.so
#6  0x00007fdff6676639 in ?? () from /usr/lib/kde4/lib/kde4/kopete_history.so
#7  0x00007fdff6675574 in ?? () from /usr/lib/kde4/lib/kde4/kopete_history.so
#8  0x00007fdff66756ad in ?? () from /usr/lib/kde4/lib/kde4/kopete_history.so
#9  0x00007fe00c7149d5 in ?? () from /usr/lib/kde4/lib/libkopete.so.4
#10 0x00007fe00a571286 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#11 0x00007fe00a5779bf in ?? () from /usr/lib/libQtCore.so.4
#12 0x00007fe00a56bd35 in QObject::event () from /usr/lib/libQtCore.so.4
#13 0x00007fe00980c54f in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0x00007fe009811125 in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0x00007fe00b380561 in KApplication::notify (this=0x7fff151dc110, 
    receiver=0x1adc870, event=0x7fff151dbdf0)
    at /build/buildd/kde4libs-4.0.80/kdeui/kernel/kapplication.cpp:311
#16 0x00007fe00a55d109 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0x00007fe00a5883dc in ?? () from /usr/lib/libQtCore.so.4
#18 0x00007fe00a585f4d in ?? () from /usr/lib/libQtCore.so.4
#19 0x00007fe004fda262 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#20 0x00007fe004fdd516 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x00007fe004fdd9af in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#22 0x00007fe00a5863af in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#23 0x00007fe00989572f in ?? () from /usr/lib/libQtGui.so.4
#24 0x00007fe00a55c585 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#25 0x00007fe00a55c6db in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0x00007fe00a55e729 in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#27 0x0000000000444031 in ?? ()
#28 0x00007fe008bca1c4 in __libc_start_main () from /lib/libc.so.6
#29 0x0000000000423a39 in _start ()
#0  0x00007fe008c49b81 in nanosleep () from /lib/libc.so.6
Comment 1 Dario Andres 2008-12-28 01:59:48 UTC
Can you still reproduce this bug with a recent KDE version? (4.1.3 / 4.2beta2 / 4.2svn) ?  Thanks :) 
Comment 2 Dario Andres 2009-02-21 14:26:30 UTC
No response from reporter. Closing as REMIND. Reopen if you still experience this. Thanks