On 11/03/15 12:47, Axel Beckert wrote:
> Simon McVittie wrote:
>> The real bug
> 
> I don't see that as bug, rather as missing feature.

You say tomato, I say tomato[en_GB] :-)

>> is that kdm and wdm do not participate in the shared
>> display-manager.service symlink management (#755359, #761642) which
>> should be fixed post-jessie.
> 
> Thanks for the reminder. Is the information about how this should be
> done still uptodate in #761642 (Cc'ed)?

I think so.

> For me the information in
> there sounds different to what you are describing above.

The complexity seen in #766462 is because gdm3's upstream-supplied
systemd service is doing unusual things (disabling the systemd unit that
would normally stop plymouth, so that it can handle that internally),
which causes bad side-effects if other DMs do not participate in the
shared management of the display-manager.service symlink. As far as
systemd is concerned, if the display-manager.service symlink points to
gdm3, it's enabled, even if its ExecStartPre is just going to bail out.

> Is there
> another _simple_ window manager whose postinst and service files I can
> use as a template?

lightdm seems to be both correct and fairly simple (in this respect),
with a simple systemd service file supplied by Debian/Ubuntu rather than
a more complex one from its upstream: see
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733220>, specifically
messages 25 and 30.

If your DM (sorry, I've lost track of which one this is!) doesn't take a
D-Bus name on the system bus, then you will need to use Type=forking or
Type=simple rather than BusName. See systemd.service(5) for full
details, but the short version is that Type=forking is for services that
use daemon(3) or similar, and Type=simple means "there is no way to tell
that this service is ready, systemd should just assume that it is".

Otherwise, lightdm's systemd hookup should be pretty similar to yours.

    S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to