Skip to content
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

Fallback to /tmp/zellij-<uid> if $XDG_RUNTIME_DIR cannot be created #3909

Open
tesuji opened this issue Jan 2, 2025 · 0 comments · May be fixed by #3910
Open

Fallback to /tmp/zellij-<uid> if $XDG_RUNTIME_DIR cannot be created #3909

tesuji opened this issue Jan 2, 2025 · 0 comments · May be fixed by #3910

Comments

@tesuji
Copy link

tesuji commented Jan 2, 2025

Updated: I found and used ZELLIJ_SOCKET_DIR in the meantime.

Recently I tried to use zellij on a shared remote Linux server (which I don't have root permissions).
zellij failed to start (which no output since it cleared the terminal buffer). I straced that down to:

1268:mkdir("/run/user/1000/zellij/0.41.2", 0777) = -1 ENOENT (No such file or directory)
1269:mkdir("/run/user/1000/zellij", 0777)    = -1 ENOENT (No such file or directory)
1270:mkdir("/run/user/1000", 0777)           = -1 EACCES (Permission denied)

$XDG_RUNTIME_DIR is /run/user/1000. However, that path doesn't exist on the server,
and even if it does, it isn't writable by normal users. Curious, I typed tmux ls and found that
tmux uses /tmp/tmux-1000/default as server path.

Could zellij fallback to somewhere in /tmp too?
Alternatively, I could kindly ask admin to support $XDG_RUNTIME_DIR.
But I don't know the infrastructure admin too well to know how long it would take.

@tesuji tesuji linked a pull request Jan 2, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant