Hi, I recently switched from cryptomator version 1.14.2 to 1.17.1. Since then I frequently experience crashes.
After a crash I can restart cryptomator, but I am not able to mount the vaults again. I get an error message “Unable to mount vault to custom path” and that I should choose a different volume type. I have to restart the system for cryptomator to work properly again.
How can I create crash reports?
I am using AppImages under Debian 13 with KDE Plasma version 6.3.6.
Thank you!
Hi,
I did a little research for you and came up with some useful information including how to remount your vaults after a crash without having to reboot Linux.
It’s a link to a note that contains information about how to increase the log detail and how to enable that so you can capture the most debug information possible and also you can try switching between fuse and web dav and see if that helps or makes a difference and it includes the location of the log files and you can open a separate terminal window and look at the logs while cryptomator is running.
Thanks! I will take a look and try it out!
Crash reports are generated automatically. They are placed in the directory from where Cryptmator is started. If there is no file, it was created in /tmp/hs_err_pid[xxx].log where [xxx] is the process id number at time of crash.
Would this command increase the debug information collected?
cryptomator --log-level TRACE
Not at all. This command does nothing.