Re: systemd breaking display manager - no way to force?

[Gunnar Wolf <gwolf@gwolf.org>]

Agustin Martin dijo [Fri, Nov 21, 2014 at 11:51:53AM +0100]:
> > > Is there *any* way to *force* systemd to start lightdm ...?
> > 
> > I have a hunch the bug is actually in lxdm (specifically the service 
> > file). It should be simple to verify:
> > 
> > - purge lxdm (remove might do it as well, but just for good measure)
> > - reconfigure lightdm (to make sure display-manager.service symlink 
> >   points to lightdm.service)
> 
> Although I am still using sysvinit I have both display managers installed
> in this sid box and to my surprise, 
> 
> /etc/systemd/system/display-manager.service
> 
> symlink is not present here, although
> 
> /lib/systemd/system/lightdm.service
> /lib/systemd/system/lxdm.service
> /lib/systemd/system/gdm3.service
> 
> are available. 
> 
> Norbert, what happens at your box? If the symlink is present, where does
> it point to?

Hi Agustin,

In my Sid machine:

$ ls -l /etc/systemd/system/display-manager.service 
lrwxrwxrwx 1 root root 35 Oct 28 12:33 /etc/systemd/system/display-manager.service -> /lib/systemd/system/lightdm.service
$ systemctl status lightdm.service 
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled)
   Active: active (running) since Fri 2014-10-31 15:18:50 CST; 3 weeks 2 days ago
     Docs: man:lightdm(1)
 Main PID: 5268 (lightdm)
   CGroup: /system.slice/lightdm.service
           ├─ 5268 /usr/sbin/lightdm
           └─25408 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

I only have one display manager installed, though, and cannot say what
would happen with others.