-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unmount does not work #233
Comments
The unmounting command should look something like below
In your case, SiriKali is failing to find "fusermount" executable |
ah I see, thanks |
This may be a stupid question, but is there a way of making SiriKali aware of the |
Where is fusermount located in your system? This commit should solve your issue. Please update your sources from git version and try again. |
but this is probably nix problem |
This should now be solved by this commit and it now shows a descriptive error when fusermount can not be found. I am not sure of a reason but there was one that made me intentionally not including the PATH variable when searching for executables. |
I think a lot of people will encounter this problem, when their distro upgrade to a newer For now, I did : |
I tried with gocryptfs version 2.4.0 and my observations are on unlocking, gocryptfs tries to use mount command and if that fails then it uses fusermount3 if available and falls back to fusermount. I think the best solution here is for gocryptfs to handle unmounting of its volume because it knows how it mounted them. The best i can do is guess work and that is not nice. In the mean time, i will try with fusermount3 if present and fall back to fusermount. |
I have opened a feature request to ask gocryptfs to also handle unmounting. |
Meanwhile, I deleted my symlink and I just installed package |
It seems SiriKali doesn't use a command for unmounting:
I'm on NixOS and built it myself (I probably forgot something?)
But I also tried a version installed through AUR on distrobox and there I get the same error
QIODevice::read (QProcess): device not open
Am I missing some option?
The text was updated successfully, but these errors were encountered: