Mojibake in non-ascii error dialogue box

Bug #777996 reported by Martin Packman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Unassigned
Breezy
Medium
Unassigned
QBzr
Medium
Unassigned

Bug Description

When qbzr displays a user error with a warning dialogue box and the message contains non-ascii characters, they get mangled even if bzr knew how to format the message as unicode.

This can be seen in the report from bug 777860 where "Baumüller" is goes through a UTF-8 -> ISO-8859-1 roundtrip:

http://najut.org/~blackarchon/error2.jpg

In qbzr.lib.trace.report_exception trying to decode the StringIO contents as UTF-8 would probably help, without needing to fix bzrlib.trace to provide a clean interface.

Related branches

Revision history for this message
Alexander Belchenko (bialix) wrote :

I'm not sure this is qbzr error. I don't remember we use such error dialogs in QBzr itself. It could be related to code in bzr-explorer

Revision history for this message
Martin Packman (gz) wrote :

The error is from bzr-explorer, the function that puts up the message box is in qbzr, and the source of the encoding mess in the first place is in bzrlib. There are things qbzr can do to make the general handling better though as this bug suggests.

Changed in qbzr:
status: New → Confirmed
importance: Undecided → Medium
Martin Packman (gz)
Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
Changed in brz:
status: New → Triaged
importance: Undecided → Medium
tags: removed: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers