Bug 13359

Summary:	isodumper, wrong place for logs
Product:	Mageia	Reporter:	Manuel Hiebel <manuel.mageia>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	sysadmin-bugs, tmb, yvesbrungard
Version:	4	Keywords:	Triaged, validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	has_procedure advisory mga4-64-ok mga4-32-ok
Source RPM:	isodumper	CVE:
Status comment:

Description Manuel Hiebel 2014-05-11 16:36:51 CEST

Description of problem:

Hello, when the copy to the usb drive is finished a popup come and says that the logs are available in the personal directory. In fact it's in the root one.

Also if you close this popup it close the apps directly.

Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2014-05-11 16:40:51 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => geiger.david68210
Summary: usbdumper, wrong place for logs and hard closing => isodumper, wrong place for logs and hard closing
Source RPM: usbdumper => isodumper

Comment 1 David GEIGER 2014-05-11 19:19:41 CEST

the bug of writing the log file in the home directory of the user is is now fixed on latest release of isodumper-0.21.

For the bug of closing the application after the writing process it will not be fixed simply because it is not possible. Isodumper can not dumper iso two times.

On Cauldron it has already been fixed, and I'll fix it yet on mga4 and on mga3.

Comment 2 David GEIGER 2014-05-11 21:44:10 CEST

isodumper-0.21.mga4 is now commited and submited on 4/Core/Updates_testing.

Can you test and confirm if this new upstream bugfix fix this bug, please ?

Comment 3 papoteur 2014-05-13 22:31:09 CEST

I just tested the version from updates-testing. isodumper.log is written in ~/.isodumper
For the close after writing, it's not a bug, it's a feature ;)

CC: (none) => yves.brungard_mageia

Comment 4 Manuel Hiebel 2014-05-13 22:33:59 CEST

yep confirmed too

Summary: isodumper, wrong place for logs and hard closing => isodumper, wrong place for logs
Whiteboard: (none) => mga4-64-ok

Comment 5 David GEIGER 2014-05-18 21:34:40 CEST

bug is now fixed on mga4 and Cauldron too.


Advisory:
========================

When the dump to the usb drive is finished a popup opens and says that the logs are available in the personal directory (~/.isodumper/isodumper.log). 
But in fact it is write in the root one (/root/.isodumper/isodumper.log).

To fix this issue, upstream has output a newer version of isodumper (v0.21) and this one fix also some other bugs.
See isodumper project changelog : 
https://github.com/papoteur-mga/isodumper/releases/tag/0.21

========================

Packages in 4/core/updates_testing:
========================
isodumper-0.21-1.mga4.noarch.rpm


Source RPM: 
========================
isodumper-0.21-1.mga4.src.rpm


How to test this update request:
========================
- Install 'isodumper' from core/release
- Choose an ISO to Dump on your usb stick
- At the end of the writing process, a "Success" window opens telling you that a log file will be written to your home directory (~/.isodumper/isodumper.log)
- Check if this file/directory has been created on your home directory.
  Normally not, as it was created in the '/root/.isodumper/isodumper.log'

- Install now 'isodumper' from core/updates_testing, redone the steps above and check if the log have been created now on your home directory.

Assignee: geiger.david68210 => qa-bugs
Whiteboard: mga4-64-ok => has_procedure mga4-64-ok

Comment 6 claire robinson 2014-05-23 15:51:21 CEST

Testing complete mga4 32
Confirmed the fix.

Validating. Advisory uploaded.

Could sysadmin please push to 4 updates

Thanks

Keywords: (none) => validated_update
Whiteboard: has_procedure mga4-64-ok => has_procedure advisory mga4-64-ok mga4-32-ok
CC: (none) => sysadmin-bugs

Comment 7 Thomas Backlund 2014-05-24 00:39:53 CEST

Update pushed:
http://advisories.mageia.org/MGAA-2014-0122.html

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED