Bug 327068 - Showing correct labels for luks-encrypted drives
Summary: Showing correct labels for luks-encrypted drives
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.1.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
: 350392 375124 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-11-03 05:55 UTC by Artur O.
Modified: 2022-11-29 05:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Artur O. 2013-11-03 05:55:53 UTC
When using luks-encrypted drives they show up in Dolhin with generic names instead of using the correct label when unmounted.

After mounting the luks-encrypted drive a new entry gets created with the the encrypted drive's label.

In the end Dolphin ends up with two entries for a encrypted drive. One entry with the generic name for example (2.7 TiB Encrypted Drive) and (Media) the label of Encrypted drive.

Selecting (Media) in places, highligts (2.7 TiB Encrypted Drive) in Places

Not exactly sure if this is a combination of solid and Dolphin or just solid.

Reproducible: Always

Steps to Reproduce:
1. Create a encrypted drive using luks and give it a label (Media in my case)
2. The drive should show up using it's generic name instead of the actual label
3. Mount the luks-encrypted drive.
Actual Results:  
Two entries now exist that point to same thing.
1,  2.7 TiB Encrypted Drive
2,  Media

Expected Results:  
Only one entry.
1,  Media
Comment 1 Jonathan Riddell 2015-03-11 19:04:05 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.
Comment 2 Artur O. 2015-03-11 19:07:45 UTC
(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.
Comment 3 Lukas Ba. 2017-01-18 17:11:27 UTC
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) ]
Comment 4 Elvis Angelaccio 2017-01-18 17:11:33 UTC
*** Bug 375124 has been marked as a duplicate of this bug. ***
Comment 5 Lukas Ba. 2017-01-20 09:37:26 UTC
Duplicate of
https://bugs.kde.org/show_bug.cgi?id=350392
Comment 6 Elvis Angelaccio 2017-01-28 21:01:30 UTC
*** Bug 350392 has been marked as a duplicate of this bug. ***
Comment 7 Justin Zobel 2022-10-30 00:37:50 UTC
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!
Comment 8 Bug Janitor Service 2022-11-14 05:14:32 UTC
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!
Comment 9 Bug Janitor Service 2022-11-29 05:17:42 UTC
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!