Dolphin Version 15.04.0 Using KDE Development Platform 4.14.10 Mounting a luks partition that has a label will throw an: "An error occurred while accessing '2.7 TiB Encrypted Drive', the system responded: The device is already mounted: Device /dev/dm-0 is already mounted at `/run/media/commander/Media'. " And mount the device. Reproducible: Always Steps to Reproduce: 1. Have a luks partition with a label ready. 2. Mount it using dolphin Actual Results: An error occurred while accessing '2.7 TiB Encrypted Drive', the system responded: The device is already mounted: Device /dev/dm-0 is already mounted at `/run/media/commander/Media'. And drive is mounted. Expected Results: No error, drive is mounted. This is probably related to Bug 350392 but wanted to split out the issues.
Thanks for the bug report. This is most likely not a Dolphin issue - we use the Solid library for mounting devices. Just to find out if this still happens in the KF5 version of Solid: Could you try if this also happens in the "File Open" dialog of KWrite and tell us about your KWrite and KDE Frameworks versions?
(In reply to Frank Reininghaus from comment #1) > Thanks for the bug report. This is most likely not a Dolphin issue - we use > the Solid library for mounting devices. Just to find out if this still > happens in the KF5 version of Solid: Could you try if this also happens in > the "File Open" dialog of KWrite and tell us about your KWrite and KDE > Frameworks versions? It does not show the red error when trying to mount with "File Open" dialog in KWrite however I still got a notification that it failed to mount while both entrys shows up in the dialog window. From the help window, KWrite Version 5.0.0 Using KDE Frameworks 5.12.0
(In reply to Artur O. from comment #2) > It does not show the red error when trying to mount with "File Open" dialog > in KWrite however I still got a notification that it failed to mount while > both entrys shows up in the dialog window. Thanks. It's not a Dolphin issue then. The file dialog uses a different error handling mechanism though, which is why you do not see the red box.
The problem persits in Frameworks 5.45 when mounting luks-devices with dolphin. Mounting any (external) luks crypted device shows the mentioned error, though the device was not previously mounted. Furthermore, Dolphins folder view does not change (ie it does not show the content of the newly mounted device). A second click on the device-symbol is required to show the content of the device.
duplicate of bug 391386 ?
The error message looks familiar. The patch for bug 370975 is apparently the fix for bug 391386. bug 370975 comment 51 mentions that the patch has already been applied in arch linux and solves the problem. If that implies that the patch has been rolled out in arch linux, then it does not fix this bug. It might be still in the testing repositories, I will keep an eye on it. Today the bug is alive and kicking in arch.
Patch for bug 370975 is in frameworks 5.46, which is now in arch. It did not resolve this bug, the error message for external luks drives persists.
Reproduced under Kubuntu 18.10 with Frameworks 5.52.0 and Dolphin 18.12.0. Tried to mount a luks-encrypted ext4 partition on an external drive in Dolphin (right-click in sidebar → "Mount"). The partition does actually get mounted (yay!), even in the mountpoint that the error message refers to, so as a user I don't understand why the error message would appear.
Bug still present on openSUSE 15.0 with solid 5.52.0. As others say, the device is mounted but the error message is annoying and makes KDE look dumb
*** Bug 402693 has been marked as a duplicate of this bug. ***