Hi Dario,

On Sun, Sep 16, 2018 at 10:59:52AM +0200, Dario Niedermann wrote:
> Il 16/09/2018 alle 10:01, Andreas Messer ha scritto:
>
> [...]
> In short: their addition was a kludge, 100% due to systemd: the only
> thing that was causing problems for them, with the X session being seen
> as "inactive", was systemd's logind component.

Thanks for pointing that out. Unfortunately, many DEs have hopped on
the systemd train and therefore depend on its services. In particular,
the missing logind was the main barrier to have DEs like Gnome or KDE
fully working on Devuan. With fully working I refer to how standard users
would expected an desktop environment to behave.

Therefor elogind was added to Devuan as a replacement for systemd's
logind. But actually elogind is just the logind component from systemd
mangled to run standalone. I expect it to show almost the same
behavior like the original one.

> So, Devuan's stock startx is running code that's only there to
> accommodate systemd, and causes incorrect/non-traditional behaviour
> on a systemd-less OS.

If we were to provide a modified version startx, we have to consider
constraints pointed out above. I'm not sure if /usr/bin/startx is
part of a packet currently manged/modified by Devuan at all.
(Most packets are original Debian ones, without any modification)

cheers,
Andreas

--
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51