Open bashfulrobot opened 1 year ago
hold up... I just noticed this when I pasted it into the issue...
statx(AT_FDCWD, "/home/dustin/.config/wpaperd/wpaperd.conf", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffd6c6b40a0) = -1 ENOENT (No such file or directory)
But the home manager module created /home/dustin/.config/wpaperd/wallpaper.toml
Will wpaperd
look for both of those files, or just /home/dustin/.config/wpaperd/wpaperd.conf
?
EDIT - checked upstream and it lists the location the home-manager module created.
So I am still stumped.
The missing daemon is a home manager problem, so please report on its repo. For what concerns the config file location, in version 0.2.0 the file was named output.conf, in version 0.3.0 it's called wallpaper.toml (https://github.com/danyspin97/wpaperd/commit/a76fb565cf6193e54022c17bb96160481a8a679e#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fcR41). wpaperd.conf and wpaperd.toml are the (old and new) other config files It could be a wpaperd bug since I don't see any attempt to open wallpaper.conf
Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:
wpaperd
either viaexec
in sway, or even at the terminalps aux
does not show any results.Expected behavior
I would have expected the app to be running as a daemon, and my wallpaper to change.
Additional context
Notify maintainers
@DPDmancul
Metadata