Bug 7512

Summary:	Wrong error message after formatting
Product:	Mageia	Reporter:	Wolfgang Bornath <molch.b>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stormi-mageia, thierry.vignaud
Version:	2	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakxtools-curses-14.22.2-1.1.mga2	CVE:
Status comment:

Description Wolfgang Bornath 2012-09-18 13:58:40 CEST

Description of problem:

I tried to add a partition with diskdrake, created in the free space on my harddisk. Adding the partition (ext4, 80GB) worked including new partition table was written to the harddisk.

The description of the partition in diskdrake said "not formatted" although the partition was displayed as red bar (ext4). Click on the button to format the partition started formatting but ended in an error message:
   "Can't use an undefined value as an ARRAY reference."

After clicking on "OK" the description of the partition still says it's unformatted. Nevertheless I tried to mount and write there, it works!

So:
1. The error message at the end of the formatting process is misleading/wrong.
2. The description "not formatted" in diskdrake for the marked partition is wrong.
3. If you want to insert a related line into fstab diskdrake rejects this, telling the partition must be formatted first.

Another user reported that the error message does not occur when formatting is doneon the CLI.

I reproduced this on 2 different machines, both with MGA2 64-Bit.

Version-Release number of selected component (if applicable):
Name        : drakxtools-curses
Version     : 14.22.2
Release     : 1.1.mga2
Architecture: x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Manuel Hiebel 2012-09-19 23:33:05 CEST

can you try the update of drakxtools in testing ?

seems a duplicate of bug 7403

Comment 2 Thierry Vignaud 2012-09-20 10:57:09 CEST

It's not

CC: (none) => thierry.vignaud

Samuel Verschelde 2013-08-29 15:37:59 CEST

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => thierry.vignaud

Comment 3 Manuel Hiebel 2013-10-22 12:21:10 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and 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.

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.

-- 
The Mageia Bugsquad

Comment 4 Manuel Hiebel 2013-11-23 16:16:38 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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