Actually, I think we can settle it that way (which would help fixing
fixing bug #770633:
Everytime we have a service which provided an alternative, we declare an
Alias=.service name. Then, we patch systemctl to
update the alternative file (if it exists) on this alias name for those
units havi
Le 24/11/2014 10:01, Sjoerd Simons a écrit :
On Mon, 2014-11-24 at 09:31 +0100, Didier Roche wrote:
Le 21/11/2014 22:46, Sjoerd Simons a écrit :
reassign 770404 lxdm
thanks
On Fri, Nov 21, 2014 at 08:01:50PM +, Simon McVittie wrote:
This looks wrong. I think it might be caused by this in
On Mon, 2014-11-24 at 09:31 +0100, Didier Roche wrote:
> Le 21/11/2014 22:46, Sjoerd Simons a écrit :
> > reassign 770404 lxdm
> > thanks
> >
> > On Fri, Nov 21, 2014 at 08:01:50PM +, Simon McVittie wrote:
> >> This looks wrong. I think it might be caused by this in lxdm.service:
> >>
> >>
Le 21/11/2014 22:46, Sjoerd Simons a écrit :
reassign 770404 lxdm
thanks
On Fri, Nov 21, 2014 at 08:01:50PM +, Simon McVittie wrote:
This looks wrong. I think it might be caused by this in lxdm.service:
[Install]
Alias=display-manager.service
Neither gdm3 nor lightdm have that,
Thank you very much, everyone, for all that detailed comments.
I remove that Alias statement and hope that fixes the problem.
Reopen the ticket if something is still wrong, please.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
clone 770404 -1
reassign -1 systemd
retitle -1 more useful error messages
severity -1 wishlist
Hi
coming back to the original bug report, I have two wishlist items:
* a way to force systemd to start a service regardless of tests
* more decent error messages, in this case it was
Error: Fi
Processing commands for cont...@bugs.debian.org:
> clone 770404 -1
Bug #770404 [lxdm] systemd: breaks lightdm, does not start anymore
Bug 770404 cloned as bug 770526
> reassign -1 systemd
Bug #770526 [lxdm] systemd: breaks lightdm, does not start anymore
Bug reassigned from package 'lxdm' to 'sys
On Fri, 21 Nov 2014, Simon McVittie wrote:
> Norbert, if I'm correct, then you should be able to fix this on your
> system with `dpkg-reconfigure lightdm` or by correcting the symlink by hand.
Indeed, or some systemctl status display-manager.service followed
by some fixes was what it fixed it for
Processing commands for cont...@bugs.debian.org:
> reassign 770404 lxdm
Bug #770404 [systemd] systemd: breaks lightdm, does not start anymore
Bug reassigned from package 'systemd' to 'lxdm'.
No longer marked as found in versions systemd/215-6.
Ignoring request to alter fixed versions of bug #77040
reassign 770404 lxdm
thanks
On Fri, Nov 21, 2014 at 08:01:50PM +, Simon McVittie wrote:
> This looks wrong. I think it might be caused by this in lxdm.service:
>
> [Install]
> Alias=display-manager.service
>
> Neither gdm3 nor lightdm have that, which suggests that it isn't
> meant t
On Fri, 21 Nov 2014 at 09:27:57 +0900, Norbert Preining wrote:
> Aehm, since yesterday or so ligthdm does not start anymore, only
> updates related were systemd, lightdm hasn't changed.
To be clear about the situation, you have lightdm, lxdm and xdm installed,
of which you intend to use lightdm; a
On Fri, 21 Nov 2014, Norbert Preining wrote:
> On Fri, 21 Nov 2014, Norbert Preining wrote:
> > Package: systemd
> > Version: 215-6
> > Severity: critical
> > Justification: breaks unrelated software
> >
> > Aehm, since yesterday or so ligthdm does not start anymore, only updates
> > related
> >
On Fri, 21 Nov 2014, Norbert Preining wrote:
> Package: systemd
> Version: 215-6
> Severity: critical
> Justification: breaks unrelated software
>
> Aehm, since yesterday or so ligthdm does not start anymore, only updates
> related
> were systemd, lightdm hasn't changed.
>
> $ systemctl status l
13 matches
Mail list logo
