Bug 363066

Summary: Luks dm-crypt encrypted disks and ROM media cannot be ejected via the filemanager
Product: [Applications] dolphin Reporter: Frank <fhenry>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 16.12.2   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Frank 2016-05-14 12:18:06 UTC 
Version 16.03.90

I use encrypted BR-Ds and dolphin detects them and mounts / decrypts them. Fine. But if one after that tries to unmount them the cryptsetup binding stays in place and they cannot be ejected unless one does a manual cryptsetup close on the automounted device.

It should not only unmount the device but also detach the cryptsetup device mapping!

Reproducible: Always

Steps to Reproduce:
1. Put in BR-D with Luks dm-crypted iso
2. open it with dolphin which asks for password and mounts it
3. Try to unmount / release / eject it via dolphin

Actual Results:  
the cryptsetup binding stays in place and they cannot be ejected unless one does a manual cryptsetup close on the automounted device.

Expected Results:  
It should not only unmount the device but also detach the cryptsetup device mapping!

It is nice that dolphin supports encrypted devices, but so far the support is "half-assed". People without a deep knowledge of the underlying encryption process will not be able to manually detach the device to eject the media.
Comment 1 Nate Graham 2017-08-18 18:30:31 UTC 
Yeah, it's definitely a bit half-baked. I'm going to mark this as a duplicate of the general "LUKS container support" bug so that we can centralize information and effort there.

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