Bug 139364 - adding existing crypto fs in yast2 partitioner takes long
Summary: adding existing crypto fs in yast2 partitioner takes long
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 4
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: Beta 3
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-15 15:35 UTC by Joachim Gleissner
Modified: 2006-01-25 16:59 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joachim Gleissner 2005-12-15 15:35:29 UTC 
When setting mount point of an existing crypto filesystem in yast2, yast2 runs an fsck on it after the user entered the passphrase. This can take a few minutes, without the user given any feedback. Is it really necessary to run fsck at this point? And if yes, a popup telling the user that it may take a moment would be really desirable imho.
Comment 1 Thomas Fehr 2005-12-15 16:30:22 UTC 
Yes, it is necessary to do a fsck to reliably detect the encryption type used.
I can add a popup but unfortunately if fsck is fast (e.g. for small fs) it will
vanish so fast that nobody can read it and this will propably confuse people
more.
Comment 2 Joachim Gleissner 2005-12-15 16:43:48 UTC 
Hm, I see. Would it be possible to have a minimum popup time?
Comment 3 Thomas Fehr 2005-12-15 16:47:32 UTC 
AFAIK there is no such functionality in YaST2 UI and I do not really want to
add a "sleep 2" or similar just to make the Popup readable in all cases.
Comment 4 Thomas Fehr 2006-01-25 16:59:42 UTC 
Now there is a popup while crypto type detection is running