systemd service failing about pacwall HOT 23 CLOSED

is this maybe because I started it with a broken config?

Pretty sure it is.

So what would fix it would be prefixing pacwall.png with cwd in main.c.

I'll probably do just this, thanks for investigating it.

from pacwall.

hook: "swaymsg output * bg $PWD/$W center '#282828'"
would work

from pacwall.

00:00:00.012 [swaymsg/main.c:417] Unable to retrieve socket path

Looks like swaymsg fails. Does running pacwall in a shell produce the same error message?

EDIT: see #46. The example hook for swaymsg is screwed, I'll fix it soon.

from pacwall.

Thanks a lot. pacwall itself is working fine

from pacwall.

I've already fixed the issue (hopefuly). Could you update pacwall-git and copy the new swaymsg hook to pacwall.conf? Please let me know if it still fails.

from pacwall.

still doesn't seem to work.
Also the $W variable seems to not work either - I copied the example config and ran pacwall.
It doesn't fail, but also doesn't show the wallpaper

➜ ~ systemctl --user status [email protected]
● [email protected] - Pacwall Wallpaper Generator
Loaded: loaded (/usr/lib/systemd/user/[email protected]; static)
Active: failed (Result: exit-code) since Mon 2020-09-14 18:04:56 CEST; 9min ago
TriggeredBy: ● pacwall-watch-updates.timer
Process: 79980 ExecStart=/usr/bin/pacwall -/ (code=exited, status=1/FAILURE)
Main PID: 79980 (code=exited, status=1/FAILURE)

Sep 14 18:04:56 arch-desktop systemd[801]: Starting Pacwall Wallpaper Generator...
Sep 14 18:04:56 arch-desktop systemd[801]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Sep 14 18:04:56 arch-desktop systemd[801]: [email protected]: Failed with result 'exit-code'.
Sep 14 18:04:56 arch-desktop systemd[801]: Failed to start Pacwall Wallpaper Generator.
➜ ~ systemctl --user status [email protected]
● [email protected] - Pacwall Wallpaper Generator
Loaded: loaded (/usr/lib/systemd/user/[email protected]; static)
Active: failed (Result: exit-code) since Mon 2020-09-14 18:12:48 CEST; 1min 56s ago
TriggeredBy: ● pacwall-watch-packages.path
Process: 84784 ExecStart=/usr/bin/pacwall -u (code=exited, status=1/FAILURE)
Main PID: 84784 (code=exited, status=1/FAILURE)

Sep 14 18:12:47 arch-desktop systemd[801]: Starting Pacwall Wallpaper Generator...
Sep 14 18:12:48 arch-desktop pacwall[84784]: 00:00:00.011 [swaymsg/main.c:417] Unable to retrieve socket path
Sep 14 18:12:48 arch-desktop systemd[801]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Sep 14 18:12:48 arch-desktop systemd[801]: [email protected]: Failed with result 'exit-code'.
Sep 14 18:12:48 arch-desktop systemd[801]: Failed to start Pacwall Wallpaper Generator.
➜ ~

from pacwall.

wait maybe I'm just an Idiot and this is an old log

pacwall-watch-packages.path loaded active waiting Run pacwall on package upgrade/removal/installation

seems to be working
as well as
pacwall-watch-updates.timer loaded active waiting Run pacwall periodically

from pacwall.

It's definitely still not showing a wallpaper for me on sway with the default config from /usr/share/pacwall/examples/hook/swaymsg

from pacwall.

It's definitely still not showing a wallpaper for me on sway with the default config from /usr/share/pacwall/examples/hook/swaymsg

What does the file look like? Is it hook: "swaymsg output \* bg '$W' center '#073642'"?

from pacwall.

Sorry for the spam, I cleared all systemd-services out and now it seems to be working fine.
(no failed units anymore! :)

the wallpaper doesn't work with $W though - config:
➜ ~ cat .config/pacwall/pacwall.conf
hook: "swaymsg output * bg '$W' center '#073642'"

from pacwall.

there is a \ before the * the formatting from github destroyed that

from pacwall.

Does something else suggested in #46 work?

from pacwall.

Actually I just figured out the problem: Apparently swaymsg doesn't accept relative paths.
So what would fix it would be prefixing pacwall.png with cwd in main.c.
So kind of not a bug on your part but should be fixed I guess :)

from pacwall.

As for the systemd services:
● [email protected] loaded failed failed Pacwall Wallpaper Generator
● [email protected] loaded failed failed Pacwall Wallpaper Generator
is this maybe because I started it with a broken config?

from pacwall.

Should be fixed in 2092e09 aka v2.0rc3.

from pacwall.

sorry to bother you again, but it still doesn't seem to work.

I can execute /usr/bin/systemd -u from cmdline normally, but apparently when triggered by systemd it fails.
Also it seems like it may have something to do with sway, because it says

Sep 17 00:26:14 arch-desktop pacwall[21716]: 00:00:00.010 [swaymsg/main.c:417] Unable to retrieve socket path

this is usually the case when either sway is not running or running in a different tty if that helps ...

➜ ~ systemctl --user status [email protected]
● [email protected] - Pacwall Wallpaper Generator
Loaded: loaded (/usr/lib/systemd/user/[email protected]; static)
Active: failed (Result: exit-code) since Thu 2020-09-17 00:26:14 CEST; 4min 24s ago
TriggeredBy: ● pacwall-watch-packages.path
Process: 21716 ExecStart=/usr/bin/pacwall -u (code=exited, status=1/FAILURE)
Main PID: 21716 (code=exited, status=1/FAILURE)

Sep 17 00:26:13 arch-desktop systemd[781]: Starting Pacwall Wallpaper Generator...
Sep 17 00:26:14 arch-desktop pacwall[21716]: 00:00:00.010 [swaymsg/main.c:417] Unable to retrieve socket path
Sep 17 00:26:14 arch-desktop systemd[781]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Sep 17 00:26:14 arch-desktop systemd[781]: [email protected]: Failed with result 'exit-code'.
Sep 17 00:26:14 arch-desktop systemd[781]: Failed to start Pacwall Wallpaper Generator.

from pacwall.

I mean it might just be, that its impossible to run swaymsg through systemd

from pacwall.

https://stackoverflow.com/questions/50311320/systemd-and-sway-socket-not-detected

maybe this helps - it seems this guy got a swaymsg background script to run via systemd

from pacwall.

Does the service succeed if you run systemctl --user import-environment SWAYSOCK by the time it's invoked?

from pacwall.

wow yeah it does !!
Anyway to automate this, or is that persistent?

from pacwall.

That is not persistent. I suppose that putting the line into the Sway startup file (does it have one?) will do fine. However, Sway could theoretically source that file before setting $SWAYSOCK.

from pacwall.

I'll test that out. Otherwise maybe putting it into the hook could work.

I guess this closes the issue though ( would be great if you put that into the README as well)

from pacwall.

Otherwise maybe putting it into the hook could work.

It does not work this way.

from pacwall.