Just did. Mounts all the file containers fine on live session.
Meaning that manjaro itself and veracrypt are not borked, which is good. Still don’t know what exactly causes the issue on the install and how to solve it
Original post was back in August, up-to-date kernel back then was 5.18.16. Today I’m rocking 6.0.9
If the above doesn’t work (bypassing VeraCrypt’s GUI), then here’s another test. (Only try the below steps if the above steps did not yield any results.)
I’m not sure how reliable (or safe) it is to use dm-crypt’s VeraCrypt/TrueCrypt container support, let alone what features it inherently works seamlessly with. But if you’re only using a passphrase (not a keyfile), and you’re not making use of “hidden volumes”, then you might be able to get away with something like this…
Create the temporary mount location if it doesn’t already exist:
sudo mkdir -p /mnt/temp
Then try to use cryptsetup to unlock the VeraCrypt container:
sudo cryptsetup open --veracrypt --type tcrypt crypt.img veracrypt1
(Replace crypt.img with your file or block-device.)
Now mount it to the temporary location (as “read-only” to play it safe for now):
sudo mount -o ro /dev/mapper/veracrypt1 /mnt/temp
Check if it mounted successfully and if you can access the files.
If successful, you can unmount and close it:
sudo umount /mnt/temp
sudo cryptsetup close veracrypt1
Just installed Manjaro and had the same issue. Uninstalled veracrypt from the software manager and downloaded and installed it from the veracrypt site. Working good.