Closed semka95 closed 8 months ago
This is because ReGreet doesn't evaluate environment variables in the [env]
section. Try entering the full path (WOBSOCK = "/run/user/1000/wob.sock"
) in the config.
But it evaluates $HOME
, for example.
Ah, interesting, that must be on greetd's side, since ReGreet has no code (as of commit f8022a0) to evaluate the values. Try asking on greetd's issue tracker.
greetd does not expand any environment variables passed in the session start command. They are set verbatim, passed to PAM and then to execve.
The reason for adding env back was primarily to allow controlling environment variables that can affect PAM modules, e.g. XDG_SESSION_CLASS
.
If one want shell expansion of environment variables, wrap the session in a shell script or prepend them to the command line (which gets passed to /bin/sh
).
@semka95 I'm going to close the issue, since there's a workaround available.
I'm setting all environment variables in
regreet.toml
in[env]
section. Variables that useXDG_RUNTIME_DIR
variable end up being not calculated, e.g if I set:WOBSOCK="$XDG_RUNTIME_DIR/wob.sock"
, it does not calculateXDG_RUNTIME_DIR
variable and in my systemWOBSOCK
variable is$XDG_RUNTIME_DIR/wob.sock
, but it should be/run/user/1000/wob.sock
. Before regreet I was using custom binary, where I set all variables before running sway, everything worked fine. How can I resolve this issue?OS: Archlinux WM: sway
regreet.toml
```toml # SPDX-FileCopyrightText: 2022 Harish Rajagopal