Description of problem: It displays the following: ??? ???? ?????? ?????.. (There was an error receiving this message. Either you and 267391043 have different encodings selected, or 267391043 has a buggy client.) However, if my buddy sends the same message while I'm online everything is ok. Version-Release number of selected component (if applicable): pidgin-2.0.1-1.fc7 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We are aware of this upstream. The submitter did not say, but based on the symptoms and the screen name (which appears to be a UIN), I surmise that this is ICQ. See http://developer.pidgin.im/ticket/1645 for progress on fixing various ICQ encoding bugs. (We have already fixed some status encoding problems there.)
This should be fixed in 2.0.2-3.fc7, please re-open if you still see this problem with that version.
I'll check that, but I can say for certain that bug with invalid encoding in tooltips remains. And messages from jaber also have invalid encoding.
Sorry, but it is not fixed. See the screenshot.
Created attachment 158092 [details] Bug-is-back screenshot
There have been a number of adjustments to how pidgin handles encodings on ICQ over the months, I'm sorry I don't know for sure if this particular issue is fixed though - can you verify if this is still a problem in Pidgin 2.3.1 ?
Checking 2.4.0 would be better.
Right, but 2.4.0 isn't in Fedora 7 stable repo yet, it is in updates-testing though.
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.