Summary: | Showing correct labels for luks-encrypted drives | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-solid | Reporter: | Artur O. <commander.alchemy> |
Component: | general | Assignee: | Lukáš Tinkl <lukas> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | kdelibs-bugs, kdeu |
Priority: | NOR | ||
Version: | 5.1.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Artur O.
2013-11-03 05:55:53 UTC
This bug is reported on libsolid which is the kdelibs4 version of the solid library. It is now in maintenance mode. If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid. (In reply to Jonathan Riddell from comment #1) > This bug is reported on libsolid which is the kdelibs4 version of the solid > library. It is now in maintenance mode. If you think it should still be > fixed in the KDE Frameworks 5 version of solid please move it to or report a > bug on frameworks-solid. Thank you, I moved it to frameworks solid and latest version available. I can confirm that solid shows two different devices for unlocked LUKS containers, the filesystem inside the container, and the partition with the container. I created a duplicate of this here, sorry. https://bugs.kde.org/show_bug.cgi?id=375124 > generic names instead of using the correct label when unmounted Regarding the label: While the LUKS container is locked/encrypted, the FSLABEL is not readable in clear text, it's encrypted, because the FSLABEL is part of the filesystem inside of the LUKS container. So dolphin/solid can't possibly show it. You can set a PARTLABEL which is saved outside of the LUKS container on the partition, and thus not encrypted. while encrypted: disk[ PARTLABEL; LUKS(????) ] when decrypted: disk[ PARTLABEL; LUKS(FSLABEL; filesystem) ] *** Bug 375124 has been marked as a duplicate of this bug. *** Duplicate of https://bugs.kde.org/show_bug.cgi?id=350392 *** Bug 350392 has been marked as a duplicate of this bug. *** Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |