-
Notifications
You must be signed in to change notification settings - Fork 19
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
Sway doesn't behave properly when ran through regreet #53
Comments
Okay I'm a little confused here. Where does this problem occur:
Also, are you saying that everything in that config file works except for the script that uses the |
Basically I'm saying the sway that is launched by regreet doesn't work. And yes, everything works in that config file except for ANY script I try. I can change the font size, and it will change the font size, but if I do an exec anything, it just refuses to even try to open it. (very strange I know, I wish I even knew where to start looking for solutions). I've done a bunch of different scripts, in a bunch of different directories. It's just my latest attempt that I tried the /tmp directory cause i knew for sure that it would have the permissions to access it. But for example, in that same config file I have an exec to a script that should set the background of my sway, where the script is located in my $HOME/scripts folder (in path). This script also just wont run (but runs on startup perfectly fine when I'm not using regreet and open sway through terminal). |
Just to clarify, everything else in the sway launched by regreet works, just not exec scripts for some reaosn |
Please post the logs, along with the contents of the Sway session file that ReGreet loads (this should be in |
I'm having the same issue in my Hyprland session meant to run Regreet. I think that greetd is the problem since it repros on gtkgreet too. This is my config for Regreet, the only things that work out of the binds and execs are the regreet one and the exit bind.
I can't find any logs since they're put in stdout which gets cleared immediately when I quit (due to greetd starting another Hyprland session immediately). Session file.
|
@Xenfo The logs should be stored in |
Just want to start by saying I am a little new at linux, but I'm pretty sure I'm doing everything right here.
Basically, in my sway config file, i have it execute a script called test which is in my /tmp/ directory (full permissions). I also have the permissions set to rwx for everyone. The only thing this script does, is make a file in my /tmp/ directory called 111. That's it. The purpose is just to see if the script is being run (ran?)
On startup, when Arch launches, this script will never be run. No matter what I do, I cannot get sway to run scripts. I've tried everything. Absolute paths, going to background, making a script launch another script, adding a delay, giving perms, etc. I've given superuser to greeter, I've given root to greeter, and nothing works.
When i launch sway normally (just by typing sway in a terminal), it all works fine though.
Before you ask,
Yes the config files are the same. When I make a change like changing the font size in that config file, the font size will change, but it just wont run exec command. Yes I've set proper permissions. Yes I'm sure the script is not working because I have another script in the sway config file that changes the background, which also doesn't work when loaded through regreet, but does through terminal.
Here's my /etc/greetd/config.toml file:
terminal]
vt = 1
[default_session]
command = "sway --config /etc/greetd/sway-config"
user = "greeter"
And here's my /etc/greetd/sway-config fle
exec "regreet; swaymsg exit"
include /home/username/.config/sway/config
the $HOME/.config/sway/config file is the one I'm trying to run the script in, but I've also tried running it in the config.toml file and the sway-config file to no avail. I've followed all the installation instructions on the regreet readme page, so I'm not sure what I could be doing wrong, other than this being a bug.
The text was updated successfully, but these errors were encountered: