Bug 156127 - chat window showing own ICQ number instead of nickname
Summary: chat window showing own ICQ number instead of nickname
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: Chat Window (show other bugs)
Version: 0.50.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-18 18:39 UTC by Unknown
Modified: 2010-06-23 16:27 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 Unknown 2008-01-18 18:39:30 UTC
Version:           0.12.7 (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.1)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-14-generic

When chatting with others using ICQ, I usually saw my nickname before the messages I sent. However, without me changing the configuration, it now sometimes displays my ICQ UID instead of my nickname. I've had the same effect about a year ago as well, but on my new PC (that is, since May 2007) so far it worked fine. Now the old problem is back. My identity settings are set to using the nickname of my ICQ account, but even setting "custom" and my nick there doesn't help. However, after changing the identity settings and restarting Kopete, it works fine in most cases and also loading the nickname from my ICQ account works. So far I couldn't find any way to reproduce that "no nickname mode" (yes, I know this way it's hard to find the cause of the problem... I'll keep looking for a pattern).
I'm using the current Kubuntu 7.10 KDE packages (3.5.8)
Comment 1 George Kiagiadakis 2008-07-24 15:02:37 UTC
I cannot reproduce this in kopete 0.50.80 using KDE 4.0.99, but I think I have seen this bug before...
Comment 2 Unknown 2009-04-30 17:56:48 UTC
I still have the issue with Kopete 0.70.2 in KDE 4.2.2, and I think I found a pattern: It seems to always happen if Kopete opens a new chat window on startup because I got offline messages. It then loads the last 5 lines of the history into the chat window, and there I see my ICQ number instead of my nickname (obviously some stuff necessary for determining the nickname is not yet loaded). Unlike with the old Kopete, messages I then send get the correct name, and closing and reopening the window also fixes the history.
Comment 3 Unknown 2009-07-20 20:37:54 UTC
One or two weeks ago, I switched to KDE 4.2.4. And for some days now, the "number instead of nickname" problem is back, but it is more resistant than it ever was. I can not make it go away - even removing ~/.kde/share/config/kopeterc and ~/.kde/share/apps/kopete does not help. After setting the account up again, no nickname is shown. Is there any other configuration file I could try to purge? I'd really like to at least work around this very old and annoying bug :(
Comment 4 Unknown 2009-07-20 21:18:09 UTC
I just tried it with a new user to make sure that it is not some other part of my KDE config which is broken - nothing changed. All I did was creating the user, running kopete as it ("kdesudo -u test kopete"), adding an ICQ connection and entering ICQ number and password. Then I send a test message to someone and the sender was shown as my number.
Comment 5 Unknown 2009-11-14 10:46:45 UTC
The issue seems to be gone :)
Comment 6 Rasto Stanik 2010-06-23 16:27:13 UTC
I've just run into the same problem with kopete 0.12.7 on KDE 3.5.10 - and I believe that the reason for this was unusually big message (probably over 50 lines, each at about 80-100 chars long) in the history of one chat in ICQ. I manually edited the file 
~/.kde/share/apps/kopete/logs/ICQProtocol/{myICQnumber}/{peerICQnumber}.{currentYearMonth}.xml 
I closed down kopete, deleted the text in the message in the log file, started kopete again and my nickname is back.

The comments above indicate that this bug is not reproducible anymore, but perhaps it would be worth to double check handling of such situation in source code (and perhaps this helps to someone running an old kopete version who runs into the same problem).