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

Issue/Question: Invalid environment block #279

Open
Aumnescio opened this issue Jan 3, 2025 · 1 comment · May be fixed by #280
Open

Issue/Question: Invalid environment block #279

Aumnescio opened this issue Jan 3, 2025 · 1 comment · May be fixed by #280

Comments

@Aumnescio
Copy link

Aumnescio commented Jan 3, 2025

I'm on Arch Linux, KDE/Wayland.

If I launch anything through swhkd, the environment apparently gets somehow messed up. For example, trying to open an image from Discord (opened with swhkd) in a browser, I get an "Invalid environment block" popup error. On a slightly deeper level, it just seems to break xdg-open.

If I open Discord just through some start menu or something non-swhkd, this issue does not exist.

Some notes:

  • I didn't install with sudo. I wonder if this could be causing issues. Both swhks and swhkd seem to be running under my user. (Edit: maybe I did install with sudo, I just installed within the home directory)
  • I noticed swhkd seems to be creating some <hash>SHELL environment variable, which gets passed down to all the children created through swhkd. This variable looked really suspicious, and is basically why I figured out swhkd was the thing causing issues.
@manthanabc
Copy link

You should be running swhks without root, while swhkd with pkexec. but i am able to reproduce this too, so probably a bug the SHELL variable is not passed correctly
minimal example would be this swhdrc

super + g 
	env > /tmp/log

and the log file has seemingly random characters appended to SHELL variable, which might be causing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants