After upgrade to the KDE 4.11.0, the LUKS encrypted drive could not be unlocked & mounted. Worked well before upgrade.

Bug #1212982 reported by Venca B Spam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dolphin (Ubuntu)
New
Undecided
Unassigned

Bug Description

Previously correct handling of LUKS encrypted devices changed after upgrade to KDE 4.11.0.

In the prevous version I had passwords stored in the kwallet and everything worked well.

After upgrade the KDE fails to unlock the LUKS device. The password is not a problem as it prompts me as usually and kwallet provides correct password to the underlying dolphin/udisks LUKS handling module.

What has been tested:
- the system correctly asks for the "main" password to the kwallet
- kwallet provides correct password
- usuall unlocking dialog shows confirmation of unlocking LUKS device
- new previously unknown dialog shows and is complaining about the missing password

Another test:
- the password ,manually retrieved from the kwallet correctly unlocks the LUKS device when used on command line (via "cryptsetup luksOpen /dev/my_encrypted_device opened_my_encrypted_device" )

Reproducible: Always

Steps to Reproduce:
1. Previous KDE installation with working opening of LUKS encrypted devices
2. Upgrade to the KDE 4.11 & reboot your system
3. After login, open Dolphin and access the encrypted drive by clicking on it in the "Devices" side bar.
4. The system will ask you for a "master" password. Enter it.
5. The system will ask you for confirmation of opening LUKS encrypted drive with preloaded password (retrieved from kwallet). Confirm it "OK".

Actual Results:
The system opens another dialog complaining and asking for the password to the LUKS device. Even when entered correct password the system next popup with error message and the LUKS device stays locked/closed.

Expected Results:
The system should unlock/open the LUKS device and mout it into the /media directory.

Just wan to stress that:
- it worked before
- the password is correct
- the dolphin acts correctly but apparently "new" dialog or layer break the think
- the underlying LUKS & cryptsetup tools & libraires works correctly
- when unlocked manualy, Dolphin can see the unlocked drive as normal device and shows it in the "Devices" sidebar.

Revision history for this message
Venca B Spam (vbspam) wrote :

Finally I found the bug is appearing in Dolphin but the root of the problem is in the polkit-1 configuration.

When edited this file:
/usr/share/polkit-1/actions/org.freedesktop.udisks2.policy

The previous behavior is back!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.