As of recently, the wlroots-based wayland compositor (and convincing Openbox replacement) LabWC 0.7.1 fails to start on Slackware current. I returns the following error/warning messages:
Code:
[libseat] [libseat/backend/logind.c:310] Could not activate session: Launch helper with unknown return code 127
[libseat] [libseat/libseat.c:79] No backend was able to open a seat
[backend/session/session.c:83] Unable to create seat: Function not implemented
[backend/session/session.c:248] Failed to load session backend
[backend/backend.c:79] Failed to start a session
[backend/backend.c:359] Failed to start a DRM session
[../src/server.c:255] unable to create backend
The moment my labwc stopped working apparently coincides with a recent polkit rebuild: polkit now uses duktape as its javascript engine instead of mozjs. In order to test whether this rebuild has anything to do with it, I built polkit locally using the official slackscript, but with the meson switch "
-Djs_engine=mozjs" instead of "
-Djs_engine=duktape", hoping to revert the change.
With my locally build polkit, labwc still doesn't start, but gives the following error:
Code:
[../src/server.c:255] unable to create backend devicesabled at compile-time
I get this same error also when I try starting LabWC using the seatd backend instead of elogind, bypassing polkit altogether.
Can anyone shed some light on how to solve these issues?
