https://bugs.kde.org/show_bug.cgi?id=395647
Bug ID: 395647
Summary: No action proposed by notifier for encrypted removable
devices (dmcrypt LUKS)
Product: plasmashell
Version: 5.12.5
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Device Notifier
Assignee: plasma-b...@kde.org
Reporter: enrico.tagliav...@gmail.com
Target Milestone: 1.0
Created attachment 113459
--> https://bugs.kde.org/attachment.cgi?id=113459&action=edit
Actions showed for normal partition, but not for dmcrypt LUKS
Description of the problem:
When a removable device with an encrypted partition is inserted the device
notifier will show it, but will propose no action for it. Clicking on the item
will do nothing. Only clicking the little "eject" icon will trigger the mount
(and, even when successful it will show an error message "You are not
authorized to mount this device"; the device is correctly accessible from
/run/media despite what the error says).
In the attached screenshot an example of the problem can be seen. This is an
external USB HDD with two partitions, first one 800 GB vfat, second one 1 TB
dmcrypt LUKS with ext4 on top. Clicking the first one will show the possible
expected list of actions, but none would be shown when clicking on the second
partition label. At least the "Open with file manager" action would be
expected, also in line with what is shown for closed Vaults.
Steps to reproduce:
1. take a removable device, such as a USB based storage
2. create at least one partition with your favorite partition editor
3. create a LUKS device on at least one of the created partitions:
cryptsetup luksFormat --cipher aes-xts-plain64 --key-size 512
--verify-passphrase /dev/path/to/partition
4. open the device to create a file system on it:
cryptsetup luksOpen /dev/path/to/partition encrypted-partition-alias
5. create the FS: mkfs.ext4 /dev/mapper/encrypted-partition-alias
6. remove the USB device, insert it again
7. check device notifier
Reproducible: always
Note clicking on the disk label used to work before. I'm not entirely sure when
it stopped as I didn't used the device very often in the last couple of months
Versions infomation:
OS: Fedora 28 up to date
Plasma: 5.12.5
kf5: 5.47 (just updated, problem was present also with 5.46)
Qt: 5.10.1
I'll try Plasma 5.13 as soon as it's released as an update in Fedora 28 and
report back.
--
You are receiving this mail because:
You are watching all bug changes.
