Bug 963130 - Some usernames are UTF-8 encoded twice
Summary: Some usernames are UTF-8 encoded twice
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Accounts
Version: 4.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 4.4
Assignee: Simon Green
QA Contact: Matt Tyson 🤬
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-15 08:06 UTC by Zdeněk Pavlas
Modified: 2018-12-09 06:29 UTC (History)
5 users (show)

Fixed In Version: 4.4.1013
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-04 01:13:41 UTC
Embargoed:


Attachments (Terms of Use)

Description Zdeněk Pavlas 2013-05-15 08:06:24 UTC
Description of problem:

Some usernames are not displayed correctly, eg. mls.  Instead of 'Michael Schröder' it's rendered as 'Michael Schröder'.

How reproducible:

Open https://bugzilla.redhat.com/show_bug.cgi?id=905209

Additional info:

u'öd'.encode('iso-8859-1') == '\xc3\xb6'
unicode('\xc3\xb6', 'utf-8') == u'ö'

There are probably more such cases.  Other accented usernames, eg mine, are displayed correctly.  It should be fairly easy to detect and fix the above cases in the user database.  (every username that's not ascii clean and could be sucessfully utf8-decoded twice is very likely mangled).  u'Zdeněk Pavlas' is correct, because ord(u'ě') > 255, and it can't be utf-8 decoded again.

Comment 4 Zdeněk Pavlas 2014-01-22 07:57:42 UTC
Apparently, not fixed: https://bugzilla.redhat.com/show_bug.cgi?id=905209#c7

Comment 5 Simon Green 2014-01-22 12:01:44 UTC
(In reply to Zdeněk Pavlas from comment #4)
> Apparently, not fixed: https://bugzilla.redhat.com/show_bug.cgi?id=905209#c7

It won't be fixed on the production server until the bug is marked CLOSED/CURRENTRELEASE. Before this however, it needs to be tested on the development and staging servers.

  -- simon

Comment 7 Jason McDonald 2014-02-04 01:13:41 UTC
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.


Note You need to log in before you can comment on or make changes to this bug.