Bug 13614

Summary:	msec-gui gives typeerror at System security tab (TypeError: not enough arguments for format string)
Product:	Mageia	Reporter:	Atilla ÖNTAŞ <tarakbumba>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia, yvesbrungard
Version:	4	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	msec-0.80.10-14.mga4.src.rpm	CVE:
Status comment:

Description Atilla ÖNTAŞ 2014-06-30 00:51:23 CEST

Description of problem:
Trying to get screenshot for MCC help file on Turkish locale Mageia 4, Mate Desktop install. I need to get http://docteam.mageia.nl/en/MCC/content/images/msecgui11.png image, of course Turkish interfaced. 

Clicking on a security setting; described like here:
http://docteam.mageia.nl/en/MCC/content/msecgui.html#d4e3144

nothing happens.

At commandline i get this error:

Traceback (most recent call last):
  File "/usr/share/msec/msecgui.py", line 1653, in option_changed
    def_start, val_def, def_end,))
TypeError: not enough arguments for format string


Version-Release number of selected component (if applicable):

msec-gui-0.80.10-14.mga4

Steps to Reproduce:
1. Open msec-gui from commandline as root: msec-gui or open it from MCC
2. Go to Security Settings tab > System security tab
3. Double click on a setting to modify the value. Nothing happens and you get the TypeError at commandline


Reproducible: 

Steps to Reproduce:

David Walser 2014-06-30 13:26:02 CEST

Assignee: bugsquad => thierry.vignaud

Manuel Hiebel 2014-06-30 19:32:06 CEST

Whiteboard: (none) => todrop?

Manuel Hiebel 2015-05-03 21:46:06 CEST

Whiteboard: todrop? => (none)

Thierry Vignaud 2015-06-11 16:19:29 CEST

CC: (none) => mageia

Thierry Vignaud 2015-06-11 16:20:01 CEST

Summary: msec-gui gives typeerror at System security tab => msec-gui gives typeerror at System security tab (TypeError: not enough arguments for format string)

Comment 1 papoteur 2015-08-01 09:08:43 CEST

Seems to to be solved in mga5.
Can you check again?
There is also a version 1.13 in updates_testing.
Papoteur

CC: (none) => yves.brungard_mageia

Thierry Vignaud 2015-08-28 10:22:42 CEST

Keywords: (none) => NEEDINFO

Comment 2 Samuel Verschelde 2015-09-21 13:19:45 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 3 Marja Van Waes 2015-10-27 06:57:04 CET

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too).

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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