Unlocking TCRYPT volume sometimes shows a confusing error message
When unlocking a volume via udisks, there is a 10 second timeout for determining the resulting cleartext object (see udisks/src/udiskslinuxencrypted.c:536). This timeout is good enough for LUKS volumes, but unlocking TCRYPT can take a lot longer, so we should increase this timeout for TCRYPT volumes.
Also, I doubt that an error message dialog shown to the user even 10 seconds after the user interaction is useful for them. The volume is still being unlocked, but the “unlocked-crypto-dev” file is not updated and the D-Bus call does not return the cleartext object. As a result, udisks doesn’t store which user unlocked the device and is therefore allowed to mount the volume, which causes #15757 (closed).
This affects upstream as well as Tails, so we should upstream the fix.
Merge request: https://github.com/storaged-project/udisks/pull/558
Feature Branch: feature/14481-TCRYPT-support-beta
Parent Task: #14480 (closed)