On Wed, Sep 24, 2014 at 09:13:15PM +0200, Yves-Alexis Perez wrote: > On mer., 2014-09-24 at 21:02 +0200, Yann Dirson wrote: > > Package: lightdm > > Version: 1.10.1-3 > > Severity: normal > > > > I have kdm set to be the default display manager, although I also have > > lightdm installed for testing purposes. > > > > After switching from sysvinit to systemd, when running > > "dpkg-reconfigure lightdm", after confirming my kdm choice, I get the > > following error: > > > > ERROR: /lib/systemd/system/kdm.service is the selected default display > > manager but does not exist > > > > This message does not occur when I do the same choice with > > "dpkg-reconfigure kdm" (which apparently does not know about systemd), > > but does not appear either when I "dpkg-reconfigure slim" (which does > > seem to know about systemd). > > My guess is that they don't handle the default display manager unit > file.
I'm not familiar with systemd yet - I assume that by "unit file" you mean something like what's described in systemd.unit(5). As far as I've understood the systemd migration, Debian should still support good old init.d scripts, which is what kdm and xdm still use. Why then would they be required to get information for a systemd-specific file, to do a job they've basically always done right ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
