Bug 25058

Summary:	Depending on invocation mode, diskdrake acts differently
Product:	Mageia	Reporter:	Frank Griffin <ftg>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, mageia, mageiatools, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-tools	CVE:
Status comment:
Attachments:	Correct display Incorrect display

Description Frank Griffin 2019-07-05 21:18:59 CEST

On a system with a single /dev/sda disk, if you invoke diskdrake through the MCC it behaves as expected, i. e. it comes up displaying all of the partitions of /dev/sda, with the widgets (like Expert Mode) in the expected place.

If you invoke it as "diskdrake" from a root command line, the partitions are  *not* displayed, and the Expert Mode widget is centered at the bottom of the window.

I'll attach screenshots showing the difference.

Comment 1 Frank Griffin 2019-07-05 21:21:18 CEST

Created attachment 11155 [details]
Correct display

Comment 2 Frank Griffin 2019-07-05 21:22:16 CEST

Created attachment 11156 [details]
Incorrect display

Comment 3 Martin Whitaker 2019-07-06 12:19:28 CEST

Isn't this bug 19171?

For me, this one comes and goes, but it is reproducible on my system at the moment.

CC: (none) => mageia

Marja Van Waes 2019-07-08 08:05:00 CEST

Keywords: (none) => NEEDINFO
CC: (none) => mageiatools, marja11

Comment 4 Morgan Leijström 2019-07-08 13:00:22 CEST

Also see Bug 24948

CC: (none) => fri

Comment 5 Frank Griffin 2019-07-08 14:47:36 CEST

(In reply to Martin Whitaker from comment #3)
> Isn't this bug 19171?
> 
> For me, this one comes and goes, but it is reproducible on my system at the
> moment.

Almost identical, but I don't remember the Expert Mode button being displaced to center as it is here.

Keywords: NEEDINFO => (none)

Comment 6 Martin Whitaker 2019-07-08 20:19:58 CEST

The screenshot attached to bug 19171 shows the Expert Mode button centred, so closing as a duplicate.

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

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