Bug 116994

Summary:	Particulary ICQ crashes on my first sent message until name of contact is changed
Product:	[Unmaintained] kopete	Reporter:	Marco Rademacher <Marco.Rademacher>
Component:	ICQ and AIM Plugins	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED REMIND
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marco Rademacher 2005-11-24 11:10:31 UTC

Version:           0.10.4 (using KDE 3.4.3 Level "b" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15-default

Sometimes when I startet kopete everything seems to work until I start to write something to another user. In the chatwindow I see my message. I get the system message in the chatwindow that I'm offline, and at the same moment a notification appears telling me that an error occured in the ICQ session and the ICQ session was closed. When I click 'OK' the whole kopete application crashes. 

This happens also mostly when I try again. In most cases, when I change something in the contact (name of the contact and/or group) everything works fine again. 

The first time this bug occured was an older kopete version, around the time when text encoding changed from latin-1 to unicode, and still it seems that most errors happen when "strange" characters are used in ICQ nicknames. 

I'm running kopete with the connections ICQ, AIM, Yahoo and MSN. 

A friend of mine also had this problem when first using kopete but only if he wrotes something to me while was using kopete, too. 
When he changed my contact name, everything worked.

Comment 1 Thiago Macieira 2005-11-24 23:35:09 UTC

Please paste the crash backtrace here.

Comment 2 Matt Rogers 2006-01-31 17:34:20 UTC

We're waiting on a crash backtrace. When you have one, please paste it here in the bug report and reopen the bug.

Comment 3 Marco Rademacher 2006-01-31 18:20:45 UTC

Hallo,

am Dienstag, 31. Januar 2006 17:34 schrieb Matt Rogers:
[bugs.kde.org quoted mail]

This crash seems to happen especially when I write an ICQ- message to short 
after starting kopete. If I'm waiting about 2 min after startup, then kopete 
will not crash. Here's the backtrace from the last crash

Good luck! :)

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 1103715584 (LWP 13270)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x4296779f in Client::start () from /opt/kde3/lib/libkopete_oscar.so.2
#5  0x42967b82 in Client::sendTyping () 
from /opt/kde3/lib/libkopete_oscar.so.2
#6  0x4295e954 in OscarContact::slotTyping ()
   from /opt/kde3/lib/libkopete_oscar.so.2
#7  0x4295ea3d in OscarContact::qt_invoke ()
   from /opt/kde3/lib/libkopete_oscar.so.2
#8  0x42919f63 in ?? () from /opt/kde3/lib/kde3/kopete_icq.so
#9  0x094f1988 in ?? ()
#10 0x00000019 in ?? ()
#11 0xbfb844c4 in ?? ()
#12 0x41dedc40 in mng_assign_bkgd () from /usr/lib/libmng.so.1
#13 0x40c811f9 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40c81c9e in QObject::activate_signal_bool ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x4007c17b in Kopete::ChatSession::myselfTyping ()
   from /opt/kde3/lib/libkopete.so.1
#16 0x4007c1b5 in Kopete::ChatSession::typing ()
   from /opt/kde3/lib/libkopete.so.1
#17 0x400bcbd2 in Kopete::ChatSession::qt_invoke ()
   from /opt/kde3/lib/libkopete.so.1
#18 0x40c811f9 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40c81c9e in QObject::activate_signal_bool ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x42c445b9 in ?? () from /opt/kde3/lib/kde3/kopete_chatwindow.so
#21 0x093ada10 in ?? ()
#22 0x0000000a in ?? ()
#23 0x00000000 in ?? ()
#24 0x409a2e38 in ?? () from /opt/kde3/lib/libkdecore.so.4
#25 0x00c44589 in ?? ()
#26 0x42c69800 in ?? () from /opt/kde3/lib/kde3/kopete_chatwindow.so
#27 0xbfb84678 in ?? ()
#28 0x42c445f6 in ?? () from /opt/kde3/lib/kde3/kopete_chatwindow.so
#29 0x093ada10 in ?? ()
#30 0x00000000 in ?? ()
#31 0xbfb84894 in ?? ()
#32 0x4123ec44 in _int_free () from /lib/tls/libc.so.6

Comment 4 Matt Rogers 2006-01-31 20:46:31 UTC

This is fixed in Kopete 0.11 (KDE 3.5.x)