Package: wdm
Version: 1.28-17
Severity: wishlist

Since the following information is helpful when a .service file for
wdm is created, but #761236 is already closed, I'm creating a new bug
report tracking this.

Here's the mail, Agustin kindly sent to #761236:

----- Forwarded message from Agustin Martin <[email protected]> -----
Date: Mon, 15 Sep 2014 12:14:07 +0200
From: Agustin Martin <[email protected]>
To: Eliad Bagherzadegan <[email protected]>, [email protected], 
[email protected]
Subject: Bug#761236: wdm does not work with systemd as the init system

Control: tag 748668 +patch
2014-09-13 10:46 GMT+02:00 Axel Beckert <[email protected]>:
> Control: affects 748668 wdm
> Control: severity 748668 important
>
> Hi Eliad,
>
> Eliad Bagherzadegan wrote:
>> On 09/12/2014 02:04 PM, Agustin Martin wrote:
>> > I guess that if you remove slim wdm will work again.
>>
>> Thank you. I actually had to purge slim for wdm to work again.
>> Sorry for the duplicate bug report and on the wrong package.
>
> You don't need to be sorry. I, as wdm package maintainer, wasn't aware
> of the issue which causes unexpected behaviour of my package and now I
> am. I probably would have found out after testing, and since you
> mentioned slim, I likely would have installed it at some point during
> testing.
>
> Thanks also to Agustin for the notice about the other report.

Hi, Axel,

Sorry, I forgot to mark this bug report as affecting wdm, thanks for doing.

IIRC, last time I looked about how other display managers deal with
this I found no info. I later switched back to sysv until I can make
two local services behave exactly as I want under systemd, so forgot
about this until now.

However seems that more info is now available, some of it from the
gnome folks. There are service files for at least gnome3 and lightdm.
lightdm is probably closer to slim (and wdm) needs and the most useful
place to look at.

References for the bug reports,

   https://bugs.debian.org/733220

Also info available in

  https://titanpad.com/s-gsprintchangelog

section "= default display manager selection ="

In short they suggest using something like

ExecStartPre=/bin/sh -c '[ ! -f /etc/X11/default-display-manager -o
"$(cat /etc/X11/default-display-manager 2>/dev/null)" =
"/usr/sbin/lightdm" ]'

but there are some other details like symlinks and aliases
discouraging to care about.

>From titanpad:

* /etc/X11/default-display-manager is and remains the definitive selection

* graphical.target has Wants=display-manager.service which provides
the dependency for auto-starting DM

* In DM packages' .service files: Don't have an [Install] section
(Dependency or Alias) as systemctl enable will otherwise make the last
installed package "win" instead of the one selected in debconf

* DM postinst: Create symlink
/etc/systemd/system/display-manager.service →
/lib/systemd/system/$(basename $(cat /e/X/d)).service

* Until all DM .services are converted: Add ExecStartPre= check that
/e/X/d is pointing to "me", and fail otherwise

I think that might be useful for fixing slim and for the future
implementation of a wdm.service file.

Regards,

-- 
Agustin
----- End forwarded message -----

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to