summaryrefslogtreecommitdiffstats
path: root/features/images
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2018-09-14 13:27:18 +0000
committerintrigeri <intrigeri@boum.org>2018-09-14 13:55:42 +0000
commit0a86adfc841b11edcdc3fdb40acb3a7e31b6d019 (patch)
tree6e260e0008fa3f7c12edf5275f9c262418552781 /features/images
parent2178fd8cf77942d9d851905e9e872450ed56fd37 (diff)
VeraCrypt test suite: give up on unmounting/locking via GNOME Files.
It is way too fragile. Nautilus will sometimes fire up a "Unable to eject 105 MB Volume" "Cannot eject drive in use: Encrypted device /dev/sda is unlocked" error dialog while according to the Journal, everything is correctly unmounted and locked by udisksd. There is probably a bug in Nautilus, GVfs, udisks, or the way they talk to each other. I've occasionally seen it for years with LUKS devices too, so this is not specific to VeraCrypt and outside of the scope of this project. So let's use udisksctl to unmount and lock VeraCrypt volumes instead. And as a consequence, no notification is displayed so instead of looking for one, let's verify that the volume was correctly unmounted (which we did already) and locked (which we did not do, we were believing the desktop notification).
Diffstat (limited to 'features/images')
-rw-r--r--features/images/NautilusFocusedEjectButton.pngbin1093 -> 0 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/features/images/NautilusFocusedEjectButton.png b/features/images/NautilusFocusedEjectButton.png
deleted file mode 100644
index 9895624..0000000
--- a/features/images/NautilusFocusedEjectButton.png
+++ /dev/null
Binary files differ