Bug 22784

Summary:	diskdrake -especially in installer- need a "wait..." message when unlocking LUKS, reading LVM
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakxtools, diskdrake	CVE:
Status comment:

Description Morgan Leijström 2018-03-16 05:02:11 CET

Description of problem:  User may think it have crashed.

__Example steps to Reproduce:

1. Have a system installed with LUKS encrypted pv for LVM in which you have i.e /, /home, swap...

0. Boot installer, select custom partitioning 

1. Select the encrypted partition, press button to unlock
-> big dialogue window appear

2. enter password, OK
-> The dialogue is replaced by big black area... during about 27 seconds(!) until it is gone and you can continue
- And that is on a modern intel i5 and 256GB nVME SSD !


An experienced user can Ctrl-Alt-F1 and watch the progress of unlocking, listing lv, activating them, etc.   But a normal user may think it have crashed.

So i propose that a message box "Please wait while unlocking and activating..." should appear after hitting that OK button.

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

(should be checked if valid on cauldron, but i guess so)

Marja Van Waes 2018-03-17 10:12:09 CET

Assignee: bugsquad => mageiatools
Source RPM: drakxtools => drakxtools, urpmi
CC: (none) => marja11

Comment 1 Morgan Leijström 2018-03-17 10:22:33 CET

Uh, names... had been up all night...

Summary: urpmi -especially in installer- need a "wait..." message when unlocking LUKS, reading LVM => diskdrake -especially in installer- need a "wait..." message when unlocking LUKS, reading LVM
Source RPM: drakxtools, urpmi => drakxtools, diskdrake

Comment 2 Morgan Leijström 2018-03-20 10:57:56 CET

OOPS, i forgot i issued it already in 2012...

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

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