fix: wlr-services might not have started services when they are disabled This can happen when the compositor exits, the services aren't stopped in time, and they crash because they can't connect to wayland display. This will make sure they get re-enabled on start of wlr-services. This shouldn't be dangerous, because wlr-services is started just once, and at worst if it was failing, it would get restarted 5 times and then disabled, leading to maximum of 5*5*(count of wlr-services) restarts, which is quite a lot, but not infinity :) Anyway wlr-services shouldn't be crashing when configured properly (what if service doesn't exist...?) so this shouldn't ever happen.
1 files changed, 5 insertions(+), 1 deletions(-) M modules/ruther/home/services/wayland.scm
M modules/ruther/home/services/wayland.scm => modules/ruther/home/services/wayland.scm +5 -1
@@ 143,6 143,9 @@ This should be called from a wayland compositor like this: `herd start wayland-d (if (service-running? display-service) (for-each (lambda (service) ;; Services might be disabled after wayland has been stopped ;; abruptly (enable-service (lookup-service service)) (start-service (lookup-service service))) '#$services) (begin @@ 159,7 162,8 @@ This should be called from a wayland compositor like this: `herd start wayland-d '#$services) (when (equal? stop-display "yes") ((@ (shepherd support) local-output) ((@ (shepherd support) l10n) "Stopping wayland-display as well.")) ((@ (shepherd support) local-output) ((@ (shepherd support) l10n) "Stopping wayland-display and x-display as well.")) (stop-service (lookup-service 'x-display)) (stop-service (lookup-service 'wayland-display))) #f)))))