OK -- I discovered the root cause of my problem and it is not a bug in
Ubuntu or cryptsetup. In my case, it was that an update on February 12
provided a new version of /sbin/blkid. This new version added a colon
to the device name for increased readability (my guess) and it broke my
script. I failed to notice the colon in log file, my test commands, and
in the strace. Sorry for wasting your time. I may file an issue with
blkid.
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => Invalid
--
cryptsetup can not access device - Command failed: Can not access device
https://bugs.launchpad.net/bugs/485624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
