-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Socket missing. #170
Comments
if you update hyprpaper to 0.6.0 you need to update hyprland to at least 0.40.0 for the socket to work |
I am running Hyprland .40. hyprctl doesn't show that, but a look at what is installed by Nix does: ls -l `which Hyprland`
lrwxrwxrwx - root 31 Dec 1969 /home/yaro/.nix-profile/bin/Hyprland -> /nix/store/2iwrx31j8vwxm7vnb9pvlhx5s2xl7ypv-hyprland-0.40.0+date=2024-05-08_36d3297/bin/Hyprland
hyprctl version
Hyprland, built from branch at commit dirty ().
Date:
Tag: , commits:
flags: (if any) Not sure why hyprctl is blank. [LOG] Welcome to hyprpaper!
built from commit v0.6.0 () |
then @fufexan for nix. My guess is |
echo $XDG_RUNTIME_DIR
/run/user/1000 Not that I mean to come off as rude, but I think this would be more productive if I'm asked versions and values of environment variables rather than presuming what they are. I'll see about installing the git version using the Flake, as I suspect I have the nixpkgs version. |
yea I made a mistake. 0.7 + 0.40. |
It seems like hyprctl hyprpaper isn't working.
Despite the fact hyprpaper is running, I get this:
Couldn't connect to /run/user/1000/hypr/_1715171536_207074319/.hyprpaper.sock. (3)
I checked and the socket is not there. I don't know where hyprpaper is putting it, but it's not being put where it's supposed to be. I even looked in /tmp on the off chance hyprpaper might still be trying to set up a socket in the old location, but there's no /tmp/hypr there.
I'm up to date on Nix with the flake.
I ran hyprpaper from a terminal and here's my output:
Looks like maybe the Nix flake is outdated?
The text was updated successfully, but these errors were encountered: