Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Weird behavior in Cryptomator vault (FUSE)

Open
#191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua, shell

Research direction

Reproduce the five-step scenario on Linux using a Cryptomator vault and an unlocked FUSE mount, then compare it with the same directory operations outside the vault. The issue names no files, tests, or entry points; done means identifying whether FUSE or Cryptomator causes the failure and documenting or resolving the compatibility behavior.

Written by the indexing model from the issue text.

Description

When using the plugin inside a Cryptomator vault, it doesn't work and triggers a very interesting error message.

  1. Download and install Cryptomator on Linux
  2. Create a new vault, unlock the vault and open a shell inside the unlocked vault (which is a FUSE mount)
  3. Create a directory inside the vault, e.g. mkdir test
  4. Change into the directory cd test
  5. Receive a weird error message:
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
Error: Could not find or load main class .home.user..local.share.sheldon.repos.github.com.skywind3000.z.lua.z.lua
Caused by: java.lang.ClassNotFoundException: /home/user//local/share/sheldon/repos/github/com/skywind3000/z/lua/z/lua

Should the plugin be compatible with FUSE or is this a known limitation? (Maybe it has nothing to do with FUSE and is a Cryptomator problem, not sure...)

Dominant language
Lua
Stars
3.1k
Forks
149
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from skywind3000/z.lua

All issues in skywind3000/z.lua

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.