[Bug 287046] New: Mounting encrypted pendrive under kde does not work
https://bugzilla.novell.com/show_bug.cgi?id=287046 Summary: Mounting encrypted pendrive under kde does not work Product: openSUSE 10.3 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: rkwasny@novell.pl QAContact: qa@suse.de Found By: --- When I insert an encrypted pendrive ( created with yast2 ) window pops "Decrypt storage device". Regardless what I enter as password i get an error: "Enclosing drive/volume is locked" partition layout: Disk /dev/sda: 1015 MB, 1015805952 bytes 16 heads, 32 sectors/track, 968 cylinders Units = cylinders of 512 * 2048 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sda1 1 478 489408 83 Linux /dev/sda2 479 968 501760 83 Linux /dev/sda1 is encrypted /dev/sda2 not mounting it using cryptsetup from console works -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=287046#c1
Will Stephenson
https://bugzilla.novell.com/show_bug.cgi?id=287046#c2
--- Comment #2 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=287046#c3
Christopher Stender
https://bugzilla.novell.com/show_bug.cgi?id=287046#c4
Will Stephenson
https://bugzilla.novell.com/show_bug.cgi?id=287046#c5
Daniel Gollub
https://bugzilla.novell.com/show_bug.cgi?id=287046#c6
Will Stephenson
https://bugzilla.novell.com/show_bug.cgi?id=287046#c7
--- Comment #7 from Will Stephenson
https://bugzilla.novell.com/show_bug.cgi?id=287046
Will Stephenson
https://bugzilla.novell.com/show_bug.cgi?id=287046#c8
--- Comment #8 from Will Stephenson
https://bugzilla.novell.com/show_bug.cgi?id=287046
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=287046#c9
Danny Kukawka
Looks like something fell off the Precipice:
#1: the semantics of hal-is-caller-locked-out (I have no idea what it means) were apparently normalized, so it returns 0 when not locked, therefore the if ["$?" != "1" ] is inverted and always thinks it's locked
No, hal-is-caller-locked-out return 0 if it's not locked and therefor the check is correct since every other value than 0 mean it's locked. The hal-is-caller-locked-out is needed to detect if the caller is allowed to use the methode. Mean: if the user is allowed via PolicyKit to access the HAL methode _and_ if the user is in a active session (via ConsoleKit) it returns 0 if not 1. This all looks correct to me. It doesn't work for you because of bug #298943.
#2: Fix that and we see that the script is called with the required variable HAL_PROP_STORAGE_ORIGINATING_DEVICE unset.
What do you mean exactly? I could not find any usage of HAL_PROP_STORAGE_ORIGINATING_DEVICE in the scripts. Only HAL_PROP_BLOCK_STORAGE_DEVICE and this variable is set correctly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=287046#c10
Will Stephenson
participants (1)
-
bugzilla_noreply@novell.com