Bug 130979

Summary:	cannot edit size of cryptoloop partition in YaST2 Partitioner (before creation)
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jens Benecke <jens-novell>
Component:	YaST2	Assignee:	Thomas Fehr <fehr>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	SUSE Linux 10.1
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST 2 logfile from /var/log/YaST2

Description Jens Benecke 2005-10-27 10:33:41 UTC

Hello,

to reproduce:
start YaST -> System -> Partitioner, ignore the warning about "experts only"
click "crypto file" (Kryptodatei in German) at the bottom of the partitioner window
create any cryptoloop file with any settings, click OK
try to edit this partition and change the size

==> the change in size is being ignored, although the partition/file hasn't even been created yet!
The y2log file does not reflect that anything in the "Size" input field has changed:

2005-10-27 12:29:54 <1> get1431p4(23208) [YCP] partitioning/custom_part_lib.ycp:829 HandlePartWidgetChanges new:$["create":true, "create_file":true, "detected_fs":`reiser, "device":"/dev/loop0", "enc_type":`twofish, "format":true, "fpath":"/home/cryptoloop", "fstopt":"loop=/dev/loop0,encryption=twofish256,user,noauto,acl,user_xattr", "fstype":"Loop Device", "inactive":true, "loop":"/dev/loop0", "mount":"/home/jens/Crypto", "name":"loop0", "noauto":true, "nr":0, "size_k":4194304, "type":`loop, "used_fs":`reiser]

This is what is logged when I try to change the partition size from "4.0 GB" to "5.0 GB". Logs attached.


Thank you,

Comment 1 Jens Benecke 2005-10-27 10:43:19 UTC

Created attachment 55694 [details]
YaST 2 logfile from /var/log/YaST2

Comment 2 Michael Gross 2005-10-27 13:33:22 UTC

I could reproduce it. No error is shown but the resize is silently ignored (and read back into the mask with the initial value).

Thomas can you take care of that?

Comment 3 Thomas Fehr 2006-01-26 17:25:24 UTC

Will be fixed in 10.1 beta#3