| Summary: | Option to only unlock LUKS device | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Bernd Steinhauser <linux> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | kfm-devel |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Exherbo | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=463870 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
SUMMARY I have an external USB storage case which I use for data storage and backups. Each of the disks is a LUKS container (yes, the whole disk, but that shouldn't matter here) and combined they hold a btrfs filesystem with raid1 profile. e.g. Backup1 LUKS ---> Backup btrfs Backup2 LUKS ---> Backup btrfs Now I do like that dolphin provides support for encrypted devices/partitions, but in such a case multiple problems arise. e.g. if only one device is present with the raid1 profile by standard it can not be mounted (because it's degraded in that state), which confuses udisks and/or dolphin. In addition, each of the devices results in a device ("Backup" in the example above), which results in unnecessary clutter, since it's the same filesystem (with the same UUID, label etc.), but that's a minor thing. A bit more critical is that if the wrong device "Backup" is selected (it is impossible to know which is the correct one), udisks and/or dolphin does not recognize whether the filesystem was mounted and tries again, which results in an endless loop which can only be stopped by killing the udisks daemon (at least I didn't find another way yet). I suspect that is because it will try to mount e.g. dm-1, but dm-0 is mounted since btrfs detects that it's the same fs and since udisks checks for dm-1 instead. This can even bring down the system, because if unnoticed it will created mount points Backup#### until the system slows down to an unresponsible state (yes, that happened to me, I think the numbers were above 2000 at that state). Might be an upstream bug, though, since it's possible udisks fault. Now, I am aware that this is a corner case, so I won't even bother with requesting all of that fixed. However, I think the easiest step (and that would already be a relieve for me) towards better support of such layouts would be if in addition to the mount option in dolphin (and actually the device notifier as well), I could also have the option to just unlock the device. That way I could prevent udisks trying to mount the fs unless all devices have been unlocked. Unlocking of multiple devices would be king, but have to be realistic here ... SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.10 / 5.20.5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION udisks is 2.9.1, in case that matters.