I have a USB drive with a luks encrypted partition. When I plug the drive, the device notifier pops up, suggesting to open the volume in the file manager. So far, so good. I click as suggested to open the volume, a window pops up to ask for the password. I enter the password and then it gets weird: 1) An error message appears with "Could not mount the following device: ......" 2) dolphin is not launched. However, the password was accepted and the device ***is in fact mounted*** despite what the error message says. Even the device notifier is aware that the device is mounted, because now there is the "unmount" icon on the right (and the icon works as expected) and there is a line representing how full the filesystem is appearing under its name. While the volume is mounted, I can click on its name in the device notifier: it still fails to launch dolphin and pops the same error message instead: "Could not mount the following device:...." So, to summarize, the device notifier works almost: the drive is mounted when the user asks, but the file manager is not launched and a false error message pops up. Remark that I can bypass entirely the device notifier: plugging the drive, ignoring the device notifier, launching dolphin and clicking on the drive from within dolphin works perfectly: my password is asked for, and the drive mounts without an error. I am running an uptodate fedora 23. I am not sure which packages are involved. I have plasma 5.5.3, kf5 5.18, dolphin 15.12, cryptsetup 1.6.8 Reproducible: Always
I forgot to mention that everything used to work fine on my fedora 21 system (with kde 4), so this is a regression.
The bug keeps being very annoying. Is there anything I can do to help debugging it ? I tried to run dbus-monitor while trying my encrypted drive, but I cannot say I understand much. So, just in case, while the drive is successfully mounted, when I click on "Open in the file manager" in the device notifier window, I don't get a dolphin window but an error message "Could not mount the following device:". Here is what happens on dbus during that time. Does it help ? ============================================================================== method call time=1455042915.689297 sender=:1.18 -> destination=org.kde.kded5 serial=2777 path=/modules/soliduiserver; interface=org.kde.SolidUiServer; member=showActionsDialog string "/org/freedesktop/UDisks2/block_devices/sdb1" array [ string "test-predicate-openinwindow.desktop" ] signal time=1455042915.692089 sender=:1.5 -> destination=(null destination) serial=5374 path=/org/kde/solid/Device__2Forg_2Ffreedesktop_2FUDisks2_2Fblock_5Fdevices_2Fsdb1; interface=org.kde.Solid.Device; member=setupRequested method return time=1455042915.694461 sender=:1.5 -> destination=:1.18 serial=5375 reply_serial=2777 signal time=1455042915.696512 sender=:1.5 -> destination=(null destination) serial=5376 path=/org/kde/solid/Device__2Forg_2Ffreedesktop_2FUDisks2_2Fblock_5Fdevices_2Fsdb1; interface=org.kde.Solid.Device; member=setupDone int32 1 string "Le périphérique est déjà monté: Device /dev/dm-5 is already mounted at `/run/media/eric/backup'. " method call time=1455042915.698572 sender=:1.75 -> destination=org.freedesktop.Notifications serial=329 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=Notify string "Hardware notifications" uint32 0 string "emblem-mounted" string "Devices notification" string "Could not mount the following device: 149,0 GiB Encrypted Drive" array [ ] array [ dict entry( string "x-kde-appname" variant string "hardwarenotifications" ) ] int32 -1 method return time=1455042915.711033 sender=:1.18 -> destination=:1.75 serial=2778 reply_serial=329 uint32 22 signal time=1455042921.045219 sender=:1.18 -> destination=(null destination) serial=2779 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=NotificationClosed uint32 22 uint32 1 signal time=1455042921.045856 sender=:1.75 -> destination=(null destination) serial=330 path=/Notify; interface=org.kde.KNotify; member=notificationClosed int32 268
After the latest series of upgrades, my fedora 23 features now plasma 5.5.4 and kf5 5.19, and this bug appears to be fixed: my encrypted drive is working fine.