BTW this error seems to be triggered by the password input mechanism - when I save the luks password "forever", volume management will always remount that enrypted device without trouble after resume.
The two other options ("forget immediately" and "forget when log out") lead to the described problem with cryptsetup failing with a "device already exists".
BTW this error seems to be triggered by the password input mechanism - when I save the luks password "forever", volume management will always remount that enrypted device without trouble after resume.
The two other options ("forget immediately" and "forget when log out") lead to the described problem with cryptsetup failing with a "device already exists".