Control: found -1 5.0.0 Control: forwarded -1 https://gitlab.freedesktop.org/wayland/weston/issues/204 Dear Hector, dear Ben, On 06/02/16 13:30, Hector Oron wrote: > On Thu, Sep 17, 2015 at 02:42:59PM -0700, Ben Longbons wrote: > >> $ weston-launch >> weston-launch: Permission denied. You should either: >> - enable systemd session support for weston-launch. >> - or add yourself to the 'weston-launch' group. > > Thanks for the report, I have been testing with 1.11.0 version and > the issue is gone on my system. Could you please re-test and update > the bug report? As the bug report title talks about Weston and not `weston-launch`, I am following up, saying that `weston --modules systemd-notify.so` does not work on a current Debian Sid/unstable system run from a tty. [10:24:41.689] fatal: drm backend should be run using weston-launch binary, or your system should provide the logind D-Bus API. [10:24:41.689] fatal: failed to create compositor backend It looks like `libdbus-1-dev` [1] is missing as a build dependency, so that support for systemd-login is *not* detected. After installing the development package, the configure output contains the line below. systemd-login support yes Can you please check the package build logs? Building with `CFLAGS=-O0 -g` I then verified, that `launcher_logind_iface` is a member of the the array `ifaces`. Kind regards, Paul [1]: https://salsa.debian.org/xorg-team/wayland/weston/blob/debian-unstable/debian/control [2]: https://packages.debian.org/search?keywords=libdbus-1-dev
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature