Summary: | UI regression when mounting LUKS-encrypted disks caused by 5d2b5180fc4d1737f12cbbaba12884dbae832823 | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-solid | Reporter: | Nate Graham <nate> |
Component: | general | Assignee: | Lukáš Tinkl <lukas> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kdelibs-bugs, meven.car, meven.car, meven29 |
Priority: | NOR | Keywords: | regression |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/frameworks/solid/commit/1d7cceda76bd3a1c2c4060d7c215ff6cbae64769 | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | Nasty error message |
Let's revert 5d2b5180fc4d1737f12cbbaba12884dbae832823 Git commit 1d7cceda76bd3a1c2c4060d7c215ff6cbae64769 by Nate Graham. Committed on 04/03/2022 at 18:50. Pushed by ngraham into branch 'master'. Revert "Don’t create a full Solid::Device to check encryption" This reverts commit 5d2b5180fc4d1737f12cbbaba12884dbae832823. This commit regressed mounting LUKS volumes; we will have to find a better way. Related: bug 398908 M +2 -3 src/solid/devices/backends/udisks2/udisksstorageaccess.cpp https://invent.kde.org/frameworks/solid/commit/1d7cceda76bd3a1c2c4060d7c215ff6cbae64769 |
Created attachment 147266 [details] Nasty error message After 5d2b5180fc4d1737f12cbbaba12884dbae832823 (confirmed with git bisect), unlocking LUKS devices suffers from a poor UI: when you try a "mount and open" from either the Disks & Devices applet or Dolphin's sidebar, you are asked for a password, but after you enter it, a nasty error message is seen. See attachment. The encrypted volume is indeed mounted and shows up in the "Devices" section of the Places panel, but does not appear as such in the "Removable Devices" section of the Places panel or the Disks & Devices applet. Instead, it shows up as locked and unmounted there; if you click on it, it asks you the password to unlock again. If you enter it, you will see a new error message explaining that it is already unlocked. This is weird and confusing and will probably trick people into thinking their data is inaccessible, which happened to me when I first encountered the problem, causing a few minutes of panic.