Bug 184159 - Status comments fom ICQ6 are broken
Summary: Status comments fom ICQ6 are broken
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kopete
Classification: Applications
Component: ICQ and AIM Plugins (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-12 17:55 UTC by Konstantin
Modified: 2009-02-13 18:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
broken comments (74.15 KB, image/png)
2009-02-12 17:57 UTC, Konstantin 		Details
All in true encoding, but not status comment (84.37 KB, image/png)
2009-02-13 14:59 UTC, Konstantin 		Details
Incorrect status (in Kopete) Correct status: ОДТЧ (94.03 KB, image/png)
2009-02-13 17:16 UTC, Konstantin 		Details
Windows-1251 Cyrillic status (25.15 KB, image/png)
2009-02-13 18:10 UTC, Roman Jarosz 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin 2009-02-12 17:55:51 UTC 
Version:           0.70.0 (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.27-11-generic

Non-Latin status comments from ICQ 6 shows like this (see in attachment)
Comment 1 Konstantin 2009-02-12 17:57:23 UTC 
Created attachment 31251 [details]
broken comments

Contact Luli has broken comment (change encoding does not help)
Comment 2 Roman Jarosz 2009-02-12 21:00:45 UTC 
I won't be able to reproduce this because I don't have Russian windows, but if you set correct encoding it should work, try UTF-8, KOI8-R or Windows-1251.
Comment 3 Konstantin 2009-02-13 14:52:47 UTC 
This does not help... But some facts (in attachment)
Comment 4 Konstantin 2009-02-13 14:59:07 UTC 
Created attachment 31269 [details]
All in true encoding, but not status comment

All in true encoding, but not status comment. This seems in broken UTF (but it is not true)
Comment 5 Roman Jarosz 2009-02-13 16:02:03 UTC 
Could you check that the status is shown correctly in some other client or catch the ICQ packets with wireshark (because if I write Russian characters in Russian official ICQ on US windows the status text which sends ICQ is mangled and there's no way how to read it even with official client)

Wireshark steps.
1. Disconnect from ICQ
2. Start wireshark.
3. From menu choose Capture->Options...
4. Choose interface probably eth0
5. Add "port 5190" (without quotes) into the combobox next to Capture Filter
button.
6. Press start.
7. Connect to ICQ and wait till you see the broken status message.
8. Press stop.
9. File->Save and save it. (and send the log to kedgedev (at) gmail.com (my email) I'll delete it right after I found what's wrong.
Comment 6 Konstantin 2009-02-13 17:16:07 UTC 
Created attachment 31272 [details]
Incorrect status (in Kopete) Correct status: ОДТЧ
Comment 7 Konstantin 2009-02-13 17:18:16 UTC 
Received from ICQ6 (another computer)
Comment 8 Roman Jarosz 2009-02-13 17:22:23 UTC 
Could you send me the wireshark log or ICQ number of some Russian ICQ 6 user so I can test it (I just need to receive the broken status message)?
Comment 9 Konstantin 2009-02-13 17:54:23 UTC 
This UIN helps you?
Comment 10 Roman Jarosz 2009-02-13 17:56:51 UTC 
Yeah helped, set contact encoding to Windows-1251 Cyrillic and relogin to ICQ
Comment 11 Konstantin 2009-02-13 18:03:19 UTC 
Can you send me your screenshot with Olga popup? Status is correct< if I do this< but comment... Or it is only Ubuntu bug.
Comment 12 Roman Jarosz 2009-02-13 18:10:56 UTC 
Created attachment 31273 [details]
Windows-1251 Cyrillic status
Comment 13 Konstantin 2009-02-13 18:19:50 UTC 
Thank you. This is only Ubuntu bug. I tested in Opensuse. It works.
Comment 14 Roman Jarosz 2009-02-13 18:24:36 UTC 
Looks like Ubuntu really broke KDE 4, I've seen more Ubuntu specific bugs :(