Le 02/12/2014 09:13, Eric Valette a écrit :
On 02/12/2014 09:01, Eric Valette wrote:
On 02/12/2014 08:55, Didier Roche wrote:
This isn't the logs we asked for though to debug your issue. Can you
paste them please? (after running as root):
systemctl status kdm.service
systemctl status display-manager.service
Here they are (making them from console :-()
-- eric
The reload message seems to imply that the kdm.service is generated
too late for the system (my system is high end quadri core (8 cpus) I7
16G RAM, fast ssd).
There is a bug in systemd when pointing in generators to mask an unit,
but it's just a cosmetic one (the proof is that the unit isn't started
and you don't have kdm ;))
For the display-manager.service not found, I have no clue except if
you gave me a wrong name.
No, that's expected in your case. I guess you don't have a
display-manager like gdm, lightdm, and so on… which have a systemd unit
file.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
