Bug 1078283 - rhnplugin crash yum when LANG do not use UTF8
Summary: rhnplugin crash yum when LANG do not use UTF8
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 2.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2014-03-19 14:26 UTC by Forlot Romain
Modified: 2017-09-28 18:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-21 09:58:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Forlot Romain 2014-03-19 14:26:29 UTC
Description of problem:
When we use yum with rhnplugin enabled and LANG set to fr_FR and repositories can't be reach then after timeout yum display following message :

 Options Error: 'utf8' codec can't decode byte 0xc1 in position 38: invalid start byte

When we launch yum with LANG set to fr_FR.UTF8, or C, it is fine. Another workaround is to disable rhnplugin but it isn't possible then to install from rhn repo.

Version-Release number of selected component (if applicable):
yum-rhn-plugin-2.0.1-1.el5

How reproducible:
Launch yum with unreachable rhn repo and LANG set to another charset than UTF8 and another language with exotic character.

Steps to Reproduce:
1. Make rhn repo unreachable
2. LANG=fr_FR yum remove <an_existing_package>
3.

Actual results:
 Loaded plugins: rhnplugin, security
 Options Error: 'utf8' codec can't decode byte 0xc1 in position 38: invalid start byte

Expected results:
Error with exotic char displayed and no yum crash.

Additional info:

Comment 1 Milan Zázrivec 2014-03-21 09:58:32 UTC
I'm wondering why you'd want to have your operating system set to
a latin1 encoding / locale. As far as french locale goes, you need
to, from the support point of view anyway, use fr_FR.UTF-8.

I'm sure there are many other places in our code which would show
similar error with non-utf8 locales.

As long as fr_FR.UTF-8 works, we have no case here, sorry.

I'm closing this with wontfix.

Comment 2 Eric Herget 2017-09-28 18:09:40 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.


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