Bug 265453

Summary: lusk disk are not properly handled on dirty remove
Product: [Unmaintained] solid Reporter: irrlicht <dr.head>
Component: libsolid-udisksAssignee: Lukáš Tinkl <lukas>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: afiestas, ht990332
Priority: NOR    
Version First Reported In: 4.9.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: the bug screenshot

Description irrlicht 2011-02-04 20:48:21 UTC 
Version:           4.6 (using KDE 4.6.0) 
OS:                Linux

So if you remove an per LUKS encrypted device without umount it by dolphin or cryptsetup and then connect it pc again. You will be prompted by KDE to enter a secret phrase. Disk get not mounted, and you'll get error:

An error occurred while accessing '465.8 GiB Encrypted Container', the system responded: org.freedesktop.UDisks.Error.Failed: Error unlocking device: cryptsetup exited with exit code 5: Device udisks-luks-uuid-2f55a6bc-85b0-409e-8cc4-82a21d1a7861-uid1000 already exists.

Device is really listed in /dev/mapper but you can't delete it by crypsetup luksClose <device> because it is "busy".


Reproducible: Always

Steps to Reproduce:
1.Plug in device
2.Dirty remove it
3.Plug in again


Actual Results:  
Device is not mounted. Restart is required.

Expected Results:  
Device should be property mounted.
Comment 1 irrlicht 2011-06-14 23:13:16 UTC 
KDE 4.6.4 still not fixed.
Comment 2 irrlicht 2011-12-08 13:48:48 UTC 
KDE 4.7.4 still not fixed.

See screenshot pls. This happends after entering RIGHT password, then dirty remove(or just type 3 times wrong root password) and you have to reboot pc to be able to mount encrypted drive by KDE again.
Comment 3 irrlicht 2011-12-08 13:49:28 UTC 
Created attachment 66501 [details]
the bug screenshot

 This happends after entering RIGHT password, then dirty
remove(or just type 3 times wrong root password) and you have to reboot pc to
be able to mount encrypted drive by KDE again.
Comment 4 irrlicht 2012-11-09 20:01:01 UTC 
Still not fixed in 4.9.3.
Comment 5 Hussam Al-Tayeb 2012-11-15 17:58:07 UTC 
I see this too. it shows the original unencypted volume and the luks opened partition which is redundant.
Comment 6 Hussam Al-Tayeb 2012-11-15 18:04:17 UTC 
I commented in wrong bug, sorry