Comment 3 for bug 1589083

I can confirm this on 16.04 32bit from a fresh minimal install.

* The container had been working fine for many years on 12.04 32bit
* The container was still working a few days ago before switching to 16.04
* cryptsetup luksOpen hangs without further notification

More accurately, using strace, it appears to be stuck on a semaphore:

# strace -p 8230
strace: Process 8230 attached
semop(65538, [{0, 0, 0}], 1^Cstrace: Process 8230 detached
 <detached ...>

(The hangs appears to happen after the mapper has been created, so one must run cryptsetup luksClose before running another luksOpen command.)

After installing the "cryptsetup" package, everything works fine again. Clearly, "cryptsetup-bin" should Depend on or at least Recommend "cryptsetup".

Ubuntu release: 16.04
Source package: cryptsetup
Package version: 2:1.6.6-5ubuntu2.1