Closed xeruf closed 4 days ago
sending a command to way-displays does not work, it says it is not running
The client determines whether the server is running by looking for a pid at /tmp/way-displays.${XDG_VTNR}.pid
. What do you see in your /tmp
?
It then finds the socket to use by looking at ${XDG_RUNTIME_DIR}/way-displays.${XDG_VTNR}.sock
. What's in your ${XDG_RUNTIME_DIR}
?
I suspect that the XDG_VTNR is different for the service. Are you using a login manager that sets 2?
trying to make changes through a plain swaymsg command (swaymsg output * scale 2) get reverted immediately by way-displays
Working as intended. way-displays will react to changes and apply its configuration. Canonical case: display arrives, sway sets it to default resolution.
this one is now clear since it is a systemd service
That's pretty cool. Can you please share your setup as a recipe?
That's pretty cool. Can you please share your setup as a recipe?
It's not by me but the fellow great manjaro-sway maintainer, see https://github.com/manjaro-sway/desktop-settings/blob/sway/community/sway/etc/systemd/user/way-displays.service :)
Seems to work fine again, I think I accidentally had two processes running as mentioned in https://github.com/alex-courtis/way-displays/issues/161
I am observing some odd behavior the last weeks:
swaymsg output \* scale 2
) get reverted immediately by way-displays