Bug 166443 - Kopete crashes when you message yourself (AIM)
Summary: Kopete crashes when you message yourself (AIM)
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: ICQ and AIM Plugins (show other bugs)
Version: 0.50.80
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on: 133621
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-13 13:57 UTC by Jonathan Thomas
Modified: 2009-04-13 14:51 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 Jonathan Thomas 2008-07-13 13:57:39 UTC
Version:           0.50.80 (using 4.00.83 (KDE 4.0.83 (KDE 4.1 Beta2), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-17-generic

Messaging yourself with the AIM protocol causes Kopete to crash.

To reproduce:
-Message your AIM account from another client, such as Pidgin.
-Watch crash. ;)

Backtrace:

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 0xb5998b40 (LWP 17350)]
[New Thread 0xb364cb90 (LWP 17377)]
[KCrash handler]
#6  0xb718cbd7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#7  0xb7ea4a2f in Kopete::ChatSession::remoteTyping ()
   from /usr/lib/kde4/lib/libkopete.so.4
#8  0xb7ea4a6c in Kopete::ChatSession::receivedTypingMsg ()
   from /usr/lib/kde4/lib/libkopete.so.4
#9  0xb383e3c4 in OscarAccount::messageReceived ()
   from /usr/lib/kde4/lib/libkopete_oscar.so.4.1.0
#10 0xb3886905 in ?? () from /usr/lib/kde4/lib/kde4/kopete_aim.so
#11 0xb3840e89 in OscarAccount::qt_metacall ()
   from /usr/lib/kde4/lib/libkopete_oscar.so.4.1.0
#12 0xb388945a in ?? () from /usr/lib/kde4/lib/kde4/kopete_aim.so
#13 0xb718c4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb718cbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb3746913 in Client::messageReceived ()
   from /usr/lib/kde4/lib/liboscar.so.1
#16 0xb374ae01 in Client::receivedMessage ()
   from /usr/lib/kde4/lib/liboscar.so.1
#17 0xb374e197 in Client::qt_metacall () from /usr/lib/kde4/lib/liboscar.so.1
#18 0xb718c4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb718cbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb37c8d03 in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#21 0xb37caf0f in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#22 0xb37cb405 in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#23 0xb379ae3d in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#24 0xb3776564 in Connection::distribute ()
   from /usr/lib/kde4/lib/liboscar.so.1
#25 0xb3776624 in Connection::streamReadyRead ()
   from /usr/lib/kde4/lib/liboscar.so.1
#26 0xb3776711 in Connection::qt_metacall ()
   from /usr/lib/kde4/lib/liboscar.so.1
#27 0xb718c4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#28 0xb718cbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#29 0xb3762d07 in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#30 0xb37609ed in ClientStream::doReadyRead ()
   from /usr/lib/kde4/lib/liboscar.so.1
#31 0xb3760d76 in ClientStream::cp_incomingData ()
   from /usr/lib/kde4/lib/liboscar.so.1
#32 0xb3760ee1 in ClientStream::qt_metacall ()
   from /usr/lib/kde4/lib/liboscar.so.1
#33 0xb718c4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#34 0xb718cbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#35 0xb3752f07 in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#36 0xb3753ac9 in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#37 0xb3753de5 in ?? () from /usr/lib/kde4/lib/liboscar.so.1
#38 0xb3760a47 in ClientStream::socketReadyRead ()
   from /usr/lib/kde4/lib/liboscar.so.1
#39 0xb3760f26 in ClientStream::qt_metacall ()
   from /usr/lib/kde4/lib/liboscar.so.1
#40 0xb718c4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#41 0xb718cbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#42 0xb71c7f87 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#43 0xb618be27 in ?? () from /usr/lib/libQtNetwork.so.4
#44 0xb617b66b in ?? () from /usr/lib/libQtNetwork.so.4
#45 0xb617c72f in ?? () from /usr/lib/libQtNetwork.so.4
#46 0xb67a9c0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#47 0xb67ae7a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#48 0xb7655d93 in KApplication::notify (this=0xbfc81178, receiver=0x858f6c0, 
    event=0xbfc80f20)
    at /build/buildd/kde4libs-4.0.83/kdeui/kernel/kapplication.cpp:311
#49 0xb71776a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#50 0xb71a2e23 in ?? () from /usr/lib/libQtCore.so.4
#51 0xb5ef8bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#52 0xb5efbe5e in ?? () from /usr/lib/libglib-2.0.so.0
#53 0xb5efc3ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#54 0xb71a2f98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#55 0xb683d1b5 in ?? () from /usr/lib/libQtGui.so.4
#56 0xb717692d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#57 0xb7176abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#58 0xb7178d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#59 0xb67a9567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#60 0x08087f6b in ?? ()
#61 0xb63cb450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#62 0x080644e1 in _start ()
#0  0xb7f41410 in __kernel_vsyscall ()
Comment 1 William Hilton 2008-08-02 18:36:54 UTC
Confirmed. Used Pidgin and Kopete on same machine. Rather than getting the typical "echo" one normally gets from messaging oneself on AIM, Kopete crashed. (Pidgin didn't though.) Using Kopete 0.50.80 with KDE 4.1.0, standard Kubuntu 8.04 packages.
Comment 2 Roman Jarosz 2008-10-16 22:28:10 UTC
Is this still valid? I can't reproduce this with Kopete 0.60.2
Comment 3 Jonathan Thomas 2008-10-16 22:33:01 UTC
Yes, it is still reproducible with Kopete 0.60.2.
Comment 4 Roman Jarosz 2008-11-08 21:47:45 UTC
Can you reproduce it with Kopete 0.60.3?
Comment 5 Jonathan Thomas 2008-11-08 21:54:18 UTC
Yes.
Comment 6 Roman Jarosz 2008-11-08 22:01:14 UTC
Could you please have a look at
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports,
try to install the debugging packages for your distribution and post a more
verbose backtrace?
Comment 7 Jonathan Thomas 2008-11-09 14:07:11 UTC
Ah, sorry. At the time I reported the bug I knew I didn't have all the debugging symbols but figured the bug was reproducible enough for that not to matter too much.

Anyway, here's a good backtrace:

Application: Kopete (kopete), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb58bb6c0 (LWP 25533)]
[New Thread 0xb341db90 (LWP 25534)]
[KCrash handler]
#6  0xb75487f7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#7  0xb7f1a44f in Kopete::ChatSession::remoteTyping (this=0x0, _t1=0x8ed0940, 
    _t2=false)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/libkopete/kopetechatsession.moc:287
#8  0xb7f1a48c in Kopete::ChatSession::receivedTypingMsg (this=0x0, 
    c=0x8ed0940, t=<value optimized out>)
    at /build/buildd/kdenetwork-4.1.3/kopete/libkopete/kopetechatsession.cpp:399
#9  0xb3582429 in OscarAccount::messageReceived (this=0x8f05048, 
    message=@0xbfb11c98)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/oscaraccount.cpp:506
#10 0xb35ddc1b in AIMAccount::messageReceived (this=0x8f05048, 
    message=@0xbfb11c98)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/aim/aimaccount.cpp:521
#11 0xb35853e5 in OscarAccount::qt_metacall (this=0x8f05048, 
    _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfb1183c)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/oscaraccount.moc:124
#12 0xb35df5fa in AIMAccount::qt_metacall (this=0x8f05048, 
    _c=QMetaObject::InvokeMetaMethod, _id=34, _a=0xbfb1183c)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/aim/aimaccount.moc:140
#13 0xb7547a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb75487e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb345d333 in Client::messageReceived (this=0x8ee3290, _t1=@0xbfb11c98)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/client.moc:293
#16 0xb34656d1 in Client::receivedMessage (this=0x8ee3290, msg=@0xbfb11c98)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/client.cpp:721
#17 0xb346904d in Client::qt_metacall (this=0x8ee3290, 
    _c=QMetaObject::InvokeMetaMethod, _id=44, _a=0xbfb11b5c)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/client.moc:220
#18 0xb7547a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb75487e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb34f6e63 in MessageReceiverTask::receivedMessage (this=0x8e55a60, 
    _t1=@0xbfb11c98)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/messagereceivertask.moc:80
#21 0xb34f9694 in MessageReceiverTask::handleType1Message (this=0x8e55a60)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/tasks/messagereceivertask.cpp:208
#22 0xb34fb0dd in MessageReceiverTask::take (this=0x8e55a60, 
    transfer=0x904ac68)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/tasks/messagereceivertask.cpp:91
#23 0xb34c05cb in Task::take (this=0x8f12f68, transfer=0x904ac68)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/tasks/task.cpp:134
#24 0xb3494ae4 in Connection::distribute (this=0x8f93548, transfer=0x904ac68)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/connection.cpp:223
#25 0xb3494ca4 in Connection::streamReadyRead (this=0x8f93548)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/connection.cpp:240
#26 0xb3494d63 in Connection::qt_metacall (this=0x8f93548, 
    _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb11f08)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/connection.moc:83
#27 0xb7547a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#28 0xb75487e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#29 0xb347dc77 in Stream::readyRead (this=0x8f12fc8)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/stream.moc:86
#30 0xb347b76d in ClientStream::doReadyRead (this=0x8f12fc8)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/oscarclientstream.cpp:327
#31 0xb347bff6 in ClientStream::cp_incomingData (this=0x8f12fc8)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/oscarclientstream.cpp:258
#32 0xb347c67b in ClientStream::qt_metacall (this=0x8f12fc8, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfb12058)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/oscarclientstream.moc:84
#33 0xb7547a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#34 0xb75487e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#35 0xb346c297 in CoreProtocol::incomingData (this=0x8ed6f2c)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/coreprotocol.moc:89
#36 0xb346d7f3 in CoreProtocol::wireToTransfer (this=0x8ed6f2c, 
    wire=@0x8ed6f34)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/coreprotocol.cpp:221
#37 0xb346e0d2 in CoreProtocol::addIncomingData (this=0x8ed6f2c, 
    incomingBytes=@0xbfb122a8)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/coreprotocol.cpp:108
#38 0xb347bd57 in ClientStream::socketReadyRead (this=0x8f12fc8)
    at /build/buildd/kdenetwork-4.1.3/kopete/protocols/oscar/liboscar/oscarclientstream.cpp:312
#39 0xb347c613 in ClientStream::qt_metacall (this=0x8f12fc8, 
    _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfb12358)
    at /build/buildd/kdenetwork-4.1.3/obj-i486-linux-gnu/kopete/protocols/oscar/liboscar/oscarclientstream.moc:88
#40 0xb7547a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#41 0xb75487e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#42 0xb7580847 in QIODevice::readyRead () from /usr/lib/libQtCore.so.4
#43 0xb60bba72 in ?? () from /usr/lib/libQtNetwork.so.4
#44 0xb60aaceb in ?? () from /usr/lib/libQtNetwork.so.4
#45 0xb60ac056 in ?? () from /usr/lib/libQtNetwork.so.4
#46 0xb6a148ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#47 0xb6a1c76e in QApplication::notify () from /usr/lib/libQtGui.so.4
#48 0xb7a72b2d in KApplication::notify (this=0xbfb129cc, receiver=0x8edb318, 
    event=0xbfb12760)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#49 0xb7532e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#50 0xb755d70a in ?? () from /usr/lib/libQtCore.so.4
#51 0xb5f146f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#52 0xb5f17da3 in ?? () from /usr/lib/libglib-2.0.so.0
#53 0xb5f17f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#54 0xb755d478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#55 0xb6aaeee5 in ?? () from /usr/lib/libQtGui.so.4
#56 0xb753152a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#57 0xb75316ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#58 0xb7533da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#59 0xb6a14767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#60 0x0808aa6f in main (argc=1, argv=0xbfb12db4)
    at /build/buildd/kdenetwork-4.1.3/kopete/kopete/main.cpp:102
#0  0xb8013424 in __kernel_vsyscall ()
Comment 8 Roman Jarosz 2008-11-09 16:44:33 UTC
Finally I can reproduce this bug. I'll try to fix it.

Btw. there is a workaround for this bug. If you have AIM screen name for instance "text1" then if you remove the old account from Kopete and add new one with screen name "Test1" then it won't crash (the screen name has to have one or more uppercase letters).
Comment 9 Roman Jarosz 2008-12-28 11:37:20 UTC
When 133621 is fixed, this bug should go away too