https://bugs.kde.org/show_bug.cgi?id=393397
--- Comment #24 from Andrius Štikonas <andr...@stikonas.eu> --- (In reply to Teddy from comment #23) > (In reply to Andrius Štikonas from comment #21) > > (In reply to Teddy from comment #20) > > > (In reply to Andrius Štikonas from comment #18) > > > > (In reply to Teddy from comment #14) > > > > > > > > Hmm, but Volume groups shouldn't be activated by just unlocking LUKS > > > > volume? > > > > It only runs "crypsetup open", so I don't understand why your Volume > > > > group > > > > is active? > > > > > > > > Maybe I'll have to test to see if I can reproduce failure to lock. > > > > > > In any case there's no option to "reactivate" the volume groups, even if I > > > click deactivate still shows deactivate, and if I refresh before locking > > > the > > > luks I have to deactivate again otherwise fails like in last attachment. > > > > This behaviour is expected. If you refresh devices before locking, KPM > > performs full rescan and reactivates all volume groups, so LUKS partition > > becomes busy. > > I did the test without refreshing, yet looks like the volume groups are > mounted anyway. If you can check it better. Maybe you can check if plasma automounter is running? I think this is the main culprint. Without automounting the current behaviour is not as bad. -- You are receiving this mail because: You are watching all bug changes.
