https://bugs.kde.org/show_bug.cgi?id=358603
Bug ID: 358603
Summary: unlocking luks encrypted drive gives an error
Product: frameworks-solid
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: lu...@kde.org
Reporter: eric.bru...@lps.ens.fr
CC: kdelibs-b...@kde.org
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
--
You are receiving this mail because:
You are watching all bug changes.
