the acquisition process is unaware of the filesystem permission of the output directory. this may lead to seemingly stalled acquisition, with only low level messages about the permission error (emitted by the python runtime).

proposed fix:
catch permission errors in filesystem writes to propagate the error to the user, to track down the permission issue (incl. indicating a failed acquisition in the process. stalling is bad ux!)
alternatively, or in addition, check write permission as part of the acquisition boot sequence (similar to the check for enough storage space on the output path)