Hello,
When X11 or Wayland crashes or gets reset (Ctrl+Alt+Backspace), mounted VeraCrypt drives disappear from the GUI. They are still mounted and visible in Nautilus, but they cannot be unmounted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This due to how the control file which stores the information about the mounted volumes and which VeraCrypt fetches in GetMountedVolumes to display them in either GUI or in CLI, is stored on /tmp/. This temporary directory is cleared in some cases, this can be a compositor crash, session loss or any way your user gets logged out. When your /tmp/ is cleared, this control file is not there, and VeraCrypt won't find any volumes, but in actuality these volumes are still mounted through device-mapper which actually does the hard work here.
I've been looking at this and working on a way to detect these "lost" mounts when VeraCrypt GUI is opened, and then a prompt would show up asking whether the user wants to dismount these volumes that are "lost". You can already get yourself out of this "broken" state by dismounting the /dev/mapper/veracryptX and then running dmsetup remove veracryptX. A more user friendly way to do this would be beneficial.
I've written something on a branch (https://github.com/Jertzukka/VeraCrypt/tree/fusectrl) that already attempts to solve this, but I need to do more testing to see how stable it is before making it as a PR.
Last edit: Jertzukka 2024-04-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
When X11 or Wayland crashes or gets reset (Ctrl+Alt+Backspace), mounted VeraCrypt drives disappear from the GUI. They are still mounted and visible in Nautilus, but they cannot be unmounted.
This due to how the control file which stores the information about the mounted volumes and which VeraCrypt fetches in GetMountedVolumes to display them in either GUI or in CLI, is stored on /tmp/. This temporary directory is cleared in some cases, this can be a compositor crash, session loss or any way your user gets logged out. When your /tmp/ is cleared, this control file is not there, and VeraCrypt won't find any volumes, but in actuality these volumes are still mounted through device-mapper which actually does the hard work here.
I've been looking at this and working on a way to detect these "lost" mounts when VeraCrypt GUI is opened, and then a prompt would show up asking whether the user wants to dismount these volumes that are "lost". You can already get yourself out of this "broken" state by dismounting the /dev/mapper/veracryptX and then running dmsetup remove veracryptX. A more user friendly way to do this would be beneficial.
I've written something on a branch (https://github.com/Jertzukka/VeraCrypt/tree/fusectrl) that already attempts to solve this, but I need to do more testing to see how stable it is before making it as a PR.
Last edit: Jertzukka 2024-04-21
For now, I'm removing it manually, but I hope that a fix will be included in one of the future updates.
On Ubuntu:
mount /media/veracryptX and dmsetup remove /dev/mapper/veracryptX
Last edit: John 2024-06-06