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

Tip of main causes all alacritty terminals to be launched at /root #296

Open
mendess opened this issue Mar 6, 2025 · 2 comments
Open

Tip of main causes all alacritty terminals to be launched at /root #296

mendess opened this issue Mar 6, 2025 · 2 comments
Assignees

Comments

@mendess
Copy link
Contributor

mendess commented Mar 6, 2025

Version Information: commit has d7182b6

  • Distribution Information Linux weatherlight 6.12.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 10 Jan 2025 00:39:41 +0000 x86_64 GNU/Linux
  • swhkd version Simple-Wayland-HotKey-Daemon 1.3.0-dev

Describe the bug:
When an alacritty terminal is spawned, it's shell working directory is /root

Expected behavior:
The shell's working directory should be ~

Actual behavior:
The shell's working directory should be /root

To Reproduce:
Install the version at the commit mentioned previously

Additional information:
I don't think this is related to alacritty, I added the following to my swhkdrc

super + N
    notify-send $PWD "$(pwd)"

and the notification I got said /root twice

@Shinyzenith
Copy link
Member

@newtoallofthis123 Can you look at this? If need be we will roll back to old security model policy.

@newtoallofthis123
Copy link
Collaborator

I am looking into it
It is not really the security model issue, but rather how we are launching the process.

When actually forking into the deescalated child process, I suppose we would have to also account for the cwd of a user since the env is being emulated.

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

No branches or pull requests

4 participants