-
-
Notifications
You must be signed in to change notification settings - Fork 102
Hyprpaper systemd service core dump on launch. #332
Copy link
Copy link
Open
Description
I enabled hyprpaper v0.8.3 service as per the wiki using
systemctl --user enable --now hyprpaper.service
Hyprland is launched through uwsm with agreeti-tuigreet
command = "tuigreet exec uwsm start hyprland.desktop"
Journalctl logs this:
Jan 31 16:27:50 mainarch systemd[1232]: Started Fast, IPC-controlled wallpaper utility for Hyprland..
Jan 31 16:27:54 mainarch hyprpaper[3671]: DEBUG ]: Welcome to hyprpaper!
Jan 31 16:27:54 mainarch hyprpaper[3671]: built from commit ()
Jan 31 16:27:54 mainarch hyprpaper[3671]: DEBUG ]: Found 2 output(s)
Jan 31 16:27:54 mainarch hyprpaper[3671]: ==========================================================================================
Jan 31 16:27:54 mainarch hyprpaper[3671]: ASSERTION FAILED!
Jan 31 16:27:54 mainarch hyprpaper[3671]: [core] Disconnected from pollfd id 0
Jan 31 16:27:54 mainarch systemd[1232]: Stopping Fast, IPC-controlled wallpaper utility for Hyprland....
Jan 31 16:27:54 mainarch hyprpaper[3671]: at: line 357 in Backend.cpp[HT] Assertion failed!
Jan 31 16:27:54 mainarch systemd[1232]: hyprpaper.service: Main process exited, code=dumped, status=6/ABRT
If i manually start the service afterward, hyprpaper starts normaly.
My config file is updated with the latest format
I reverted to starting with:
exec-once = uwsm app -- hyprpaper
I assume it has something to do with a race condition on launch? I tried to set a 1 second delay to restart, but i get the same issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels