Kopete Crashes when Self is IM'd

Bug #108075 reported by Fred Benenson
8
Affects Status Importance Assigned to Milestone
KDE Network
Fix Released
High
kdenetwork (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kopete

When logged in and sent a message from another terminal logged in through another client system (Meebo, AIM on Windows, iChat, etc.) to the user's own AIM screen name, Kopete crashes. Also, in contrast with virtually every other IM client out there, it doesn't allow for adding oneself to one's own buddy list.

Tags: kopete
Revision history for this message
Marcus Asshauer (mcas) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in kdenetwork:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Yup, still crashes with Kopete 4.0.83.

Changed in kdenetwork:
status: Incomplete → Confirmed
Revision history for this message
Fred Benenson (fcb) wrote : Re: [Bug 108075] Re: Kopete Crashes when Self is IM'd

Thanks. :)

On Sat, Jul 12, 2008 at 10:05 PM, Jonathan Thomas <email address hidden>
wrote:

> Yup, still crashes with Kopete 4.0.83.
>
> ** Changed in: kdenetwork (Ubuntu)
> Status: Incomplete => Confirmed
>
> --
> Kopete Crashes when Self is IM'd
> https://bugs.launchpad.net/bugs/108075
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Jonathan Thomas (echidnaman) wrote :
Download full text (4.6 KiB)

More accurately this crash occurs with Kopete 0.50.80, which is included in kdenetwork 4.0.83.

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 0xb71c...

Read more...

Changed in kdenetwork:
status: Unknown → New
Changed in kdenetwork:
status: New → Confirmed
Changed in kdenetwork:
importance: Undecided → Low
status: Confirmed → Triaged
capi /. (barraponto)
tags: added: kopete
Changed in kdenetwork:
status: Confirmed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed in KDE 4.3 beta1.

Changed in kdenetwork (Ubuntu):
status: Triaged → Fix Released
Changed in kdenetwork:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.