On 2024-04-19 19:33, -pj wrote:
On 04-19-2024 11:44AM, Carlos E. R. wrote:
On 2024-04-19 15:44, -pj wrote:
Hi, the machine is running openSUSE Tumbleweed 20240417. I am not able to mount an external encrypted usb any longer by using System Tray method (just noticed, from Plasma 6 System Tray). I have not attempted using Snapper to rollback the OS yet.
...
It seems as if something with how Plasma 6 uses luksOpen has broken. I have not used the following in Konsole yet - cryptsetup luksOpen /dev/sdc cr_ARBITRARY_NAME *because* I do not think I should have to do this with the volume already having a name.
This name is not the disk or partition name. It is just the name of the internally used device name. It can be a completely random name.
I understand that much I think you mean the name that 'Device mapper' assigns it for the particular instance?
Except that the name assignation is not automatic. The command call to cryptsetup assigns the name you decide.
It appears there is a new Tumbleweed snapshot available. The following product is going to be upgraded: openSUSE Tumbleweed 20240417-0 -> 20240418-0
Do you think I should attempt to update the machines OS and see if it resolves?
No idea, I don't use TW.
Telcontar:~ # l /dev/mapper/ total 0 drwxr-xr-x 2 root root 80 Apr 18 13:23 ./ drwxr-xr-x 21 root root 6280 Apr 19 07:26 ../ crw------- 1 root root 10, 236 Apr 18 13:22 control lrwxrwxrwx 1 root root 7 Apr 18 13:23 cr_cripta -> ../dm-0 Telcontar:~ #
Thinkcentre-M57p:~ # l /dev/mapper total 0 drwxr-xr-x 2 root root 140 Apr 19 08:12 ./ drwxr-xr-x 20 root root 4720 Apr 19 11:39 ../ lrwxrwxrwx 1 root root 7 Apr 19 07:36 Lenovo_M57p-openSUSE_Tumbleweed -> ../dm-0 crw------- 1 root root 10, 236 Apr 19 07:36 control lrwxrwxrwx 1 root root 7 Apr 19 08:12 sdb_crypt -> ../dm-3 lrwxrwxrwx 1 root root 7 Apr 19 07:36 system-root -> ../dm-2 lrwxrwxrwx 1 root root 7 Apr 19 07:36 system-swap -> ../dm-1
The encrypted partition on the usb device is displaying as "sdb_crypt" above I think.
cryptsetup status sdb_crypt will tell you what disk/partition it is.
When you mount it via desktop automatic doings, the desktop assigns it a name, which can be random or obtained "somehow".
I see now that the desktop assigns the usb a "Device mapper" name "somehow". On this devices encrypted partition I have previously labeled it a specific name and when it used to be mounted the name 'WORLDWIDE1' would identify it in Dolphin. Also in Konsole I believe (/run/media/username/WORLDWIDE1).
That name is usually the label of the filesystem if it has one. Otherwise it might use the GPT label, if it exists. If not, I dunno what name it uses. So be sure to assign labels to your partitions.
A different machine... laptop here is using an old version of Tumbleweed 32 bit 20240310 and the desktop allows for unlocking still. Passing: # l /dev/mapper then displays the device as - luks-fd28e551-c765-461e-aab0-a2c49bb786b9 -> /dm-4 <- So that is it's ARBITRARY_NAME for the session.
The luks.... one, yes.
The issue is that I can not mount it "via desktop automatic doings" anymore. Do you think I should attempt to file a bug report about this?
🫥
Probably. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)