This seems to be because there is a (known and expected) delay between the loopback device being registered and udisks getting to know (via udev) about it. Loïc says we could workaround it by running 'udevadm settle' before using udisks but ideally we should stick to a single tool for both the registration and later lookup.
This seems to be because there is a (known and expected) delay between the loopback device being registered and udisks getting to know (via udev) about it. Loïc says we could workaround it by running 'udevadm settle' before using udisks but ideally we should stick to a single tool for both the registration and later lookup.