Bug 395647 - No actions for encrypted removable devices until plasmashell is restarted
Summary: No actions for encrypted removable devices until plasmashell is restarted
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Disks & Devices (show other bugs)
Version: 5.12.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
: 452926 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-06-20 12:02 UTC by Enrico Tagliavini
Modified: 2022-04-25 18:25 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Actions showed for normal partition, but not for dmcrypt LUKS (55.07 KB, image/png)
2018-06-20 12:02 UTC, Enrico Tagliavini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Enrico Tagliavini 2018-06-20 12:02:38 UTC
Created attachment 113459 [details]
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.
Comment 1 Christoph Feck 2018-09-06 20:07:14 UTC
I am using zuluCrypt GUI to mount encrypted volumes, but would indeed be nice if it was possible directly from Plasma device list.
Comment 2 Nico Dorn 2018-11-03 08:45:10 UTC
Confirmed!

OS: Ubuntu (bionic) with KDE neon 5.14.2
Frameworks: 5.51.0
Qt: 5.11.2
Comment 3 Canoe 2018-11-05 19:32:17 UTC
Confirmed : 
4.19.0-4-MANJARO
LSB Version:    n/a
Distributor ID: ManjaroLinux
Description:    Manjaro Linux
Release:        18.0.0
Codename:       Illyria

Plasma 5.14.2
Frameworks 5.51.0
Qt 5.11.2
Comment 4 Jim Jones 2018-12-18 22:19:45 UTC
same problem here

Plasma 5.14.4
Frameworks 5.53.0
Qt 5.11.3
Comment 5 Jim Jones 2018-12-18 22:22:11 UTC
restarting plasma with

kquitapp5 plasmashell
/usr/bin/plasmashell &

also "fixes" the problem after "You are not authorized to mount this device" is shown and i can select "Open with File Manager". But the restart has to be done after a new encrypted devices gets unlocked
Comment 6 Momus 2019-07-28 03:29:05 UTC
Confirmed on Debian 10 Buster.

Also, I note that it worked correctly on KDE4 on Debian 9 Stretch, so this is a regression.
Comment 7 Nate Graham 2020-11-25 00:06:07 UTC
This is still an issue in Plasma 5.20 with the new UI.
Comment 8 Nate Graham 2021-05-07 17:46:49 UTC
Once the device is mounted, the actions are still not visible for me, but restarting plasmashell fixes it. So there must be an issue somewhere of the new status not propagating to the UI automatically.
Comment 9 Nate Graham 2022-04-25 18:25:08 UTC
*** Bug 452926 has been marked as a duplicate of this bug. ***