Bug 16204 - msec-gui: error message and does not work ('ascii' codec can't decode byte 0xc3 in position 16)
Summary: msec-gui: error message and does not work ('ascii' codec can't decode byte 0x...
Status: RESOLVED DUPLICATE of bug 13837
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-24 23:04 CEST by macxi
Modified: 2015-07-04 11:26 CEST (History)
4 users (show)

See Also:
Source RPM: msec-gui-1.11-2.mga5.x86_64.rpm
CVE:
Status comment:


Attachments

Description macxi 2015-06-24 23:04:17 CEST
Description of problem:
When I try to access the Mageia Control Center MCC-in "Security" tab and try to access "Security Configuration and system audit",  the error message appears: "This program was not closed properly"

This error occurs in Mageia 5, KDE 64, with the "Portuguese of Brazil language", instaled in Virtualbox and other Mageia 5 KDE 64 instaled in real machine. 

I can access the ms-gui and configure it correctly in Mageia 5 KDE 64 with English language (American)

Is the same Bug 13837 of Cauldron

Version-Release number of selected component (if applicable):
msec-gui-1.11-2.mga5.x86_64.rpm

How reproducible:
This error always occurs when I try to configure Msec-gui through MCC

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-07-03 22:52:58 CEST
Confirming for 32bit:

When starting MCC with 

LANGUAGE=pt_BR mcc

and clicking on the icon to select msec-gui, I get a message "Este Programa não foi Encerrado Corretamente"

Starting the tool directly fails. too:

[root@Mga5_32bit marja]# LANGUAGE=pt_BR msecgui 
INFO: Starting gui..
Traceback (most recent call last):
  File "/usr/share/msec/msecgui.py", line 1789, in <module>
    gui = MsecGui(log, msec, perms, msec_config, perm_conf, exceptions, embed=PlugWindowID)
  File "/usr/share/msec/msecgui.py", line 173, in __init__
    self.reload_config()
  File "/usr/share/msec/msecgui.py", line 457, in reload_config
    self.exceptions.load()
  File "/usr/share/msec/config.py", line 319, in load
    self.log.info(_("loading exceptions file %s: %s") % (self.config, sys.exc_value[1]))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 16: ordinal not in range(128)
[root@Mga5_32bit marja]#

Which character on that line has position 16? The "i" in "arquivo"? At first sight, I see nothing odd.
  #: ../src/msec/config.py:319
  msgid "loading exceptions file %s: %s"
  msgstr "Carregando arquivo de exceções %s: %s"


Starting it with LANGUAGE=pt msecgui doesn't give an error.

The following error is valid for pt.po, too, so probably unrelated:

  [marja@Mga5_32bit ~]$ LC_ALL=C msgfmt -c -v mgagit/software/msec/po/pt_BR.po 
  pt_BR.po:19: warning: header field 'Content-Transfer-Encoding' still has the
  initial default value
  318 translated messages.
  [marja@Mga5_32bit ~]$

Asssigning to i18n-bugs

CC: (none) => marja11
Hardware: x86_64 => All
Assignee: bugsquad => i18n-bugs
Summary: msec-gui: error message and does not work => msec-gui: error message and does not work ('ascii' codec can't decode byte 0xc3 in position 16)

Comment 2 Filip Komar 2015-07-03 23:19:42 CEST
I think we can't force translators to change string(s) to the ASCII encoding.

At least until Thierry decide. I hope that I'm right about that he maintain the package. At least I see in madb that he mostly commit to it. Feel free to reasign.

CC: (none) => filip.komar
Assignee: i18n-bugs => thierry.vignaud

Comment 3 Mageia Robot 2015-07-04 00:11:23 CEST
commit dc391c03b41b0aac4e397e7724370db24be775b4
Author: Marja van Waes <marja@...>
Date:   Sat Jul 4 00:10:50 2015 +0200

    add missing underscores and encoding, even if prolly unrelated (mga#16204)
---
 Commit Link:
   http://gitweb.mageia.org/software/msec/commit/?id=dc391c03b41b0aac4e397e7724370db24be775b4
Comment 4 Marja Van Waes 2015-07-04 11:03:49 CEST
(In reply to Filip Komar from comment #2)
> I think we can't force translators to change string(s) to the ASCII encoding.
> 

I don't think that's the problem, even if I don't understand what is, except that there is a good chance it is something in the pt_BR po file (but maybe a different line than I first thought)

CC'ing Yuri who might understand whether anything is wrong with pt_BR.po (note that I made some changes that might not have been copied to Tx).

Also CC'ing papoteur, who knows python and might be able to tell where the following points to:
    File "/usr/share/msec/config.py", line 319, in load
    self.log.info(_("loading exceptions file %s: %s") % (self.config, sys.exc_value[1]))

(it is maybe a translation for the target that contains an error, instead of the translation for "loading exceptions file %s: %s"?
.... grep -r "sys.exc_value" software/msec/* gives many lines that contain a translatable string)

Btw, what is the command to get all lines in a po file wrapped at 79 characters (including getting any """ added or moved where needed)?

It is hard to check the current pt_BR.po, because it contains some very long lines :-/

CC: (none) => yurchor, yves.brungard_mageia

Comment 5 papoteur 2015-07-04 11:26:51 CEST
I think this is a duplicate.
https://bugs.mageia.org/show_bug.cgi?id=13837#c13

*** This bug has been marked as a duplicate of bug 13837 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


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