7b8fec1af4
Luks2.unlock() ran 'cryptsetup open' with no error handling, so a failure raised a bare CalledProcessError. Python renders that exception with only the exit status and discards the captured output, so cryptsetup's stderr (merged into stdout by run()) never reached the install log. encrypt() already wraps its cryptsetup call and raises a DiskError that includes the captured output. Mirror that for unlock() so a failure reports the actual cryptsetup message instead of an opaque traceback. Reported in #4327, where the underlying 'device-mapper: crypt: unknown table type' error was hidden from the log for this reason. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| device_handler.py | ||
| disk_menu.py | ||
| encryption_menu.py | ||
| fido.py | ||
| filesystem.py | ||
| luks.py | ||
| lvm.py | ||
| partitioning_menu.py | ||
| subvolume_menu.py | ||
| utils.py | ||