Managed to mount veracrypt file container through cryptsetup using sudo cryptsetup open --type tcrypt --veracrypt ~/file/path veracrypt. The container shows up as loopback device with unknown content.
While troubleshooting another issue, had to use xhost si:localuser:root. Veracrypt still fails to mount any file containers while running as user. Running veracrypt as root seems to work now.
I can’t find any mention of the --veracrypt part of that command in the cryptsetup manual page.
Perhaps it’s just: sudo cryptsetup open --type tcrypt ~/file/path veracrypt
?
Just letting everyone know that Veracrypt still fails to mount any container as user with the same error
Mounting containers after launching Veracrypt with sudo works ONLY AFTER setting xhost si:localuser:root
While mounting as root, veracrypt keeps spamming to stdout (veracrypt:497552): dconf-WARNING **: 15:30:41.416: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=0656786ec708423786c0c707c178f4fd --binary-syntax --close-stderr”: Child process exited with code 1
There is the simple alternative of Veracrypt: SiriKali supports many different encryption algorithms for encrypted folders. Any volume size is flexible.
I have been using veracrypt on Manjaro for years without problems. At least it’s not a general problem. It’s something with your configuration it seems.
So I’ve tried running veracrypt on GNOME X11 session and KDE X11 session.
I’ve also tried creating new user and running veracrypt under GNOME X11 and GNOME Wayland.
Exactly, im using Veracrypt on the KDE Desktop with the GUI and the only problem that i have that the GUI Showed a assertion bug when i click on: Select Device.
I can still ignore this error and keep going on, everything else works as intended.
But on the other side, im not using this container files in Veracrypt.