You are not logged in.
Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
Last edited by nierro (2012-07-15 17:13:42)
Offline
Hi!
After the upgrade of systemd, i noticed today this error in dmesg:systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
systemctl status display-manager.service display-manager.service Loaded: error (Reason: No such file or directory) Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
There has been a change regarding display managers. up until now they were WantedBy graphical.target, which was kind of stupid because this allowed you to enable multiple display managers.
Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it.
Offline
It was so easy, damn!
Thank you very much for the explanation!
Offline
thanks fixed mine also
Offline
Didn't work for me. I use LXDM, and i tried systemctl reenable lxdm.service.
oldpond = glide
Offline
Didn't work for me. I use LXDM, and i tried systemctl reenable lxdm.service.
seems like lxdm hasn't been updated yet.
It was fixed in git but the new version hasn't been released yet: https://projects.archlinux.org/svntogit … cc2afee8b9
just wait for the lxdm update and then try again. As far as I can see the error message can be safely ignored until then.
Offline
Thank you 65kid for the KISS explanations and nierro for asking
Now that I have slim boot manager back, want to try auto-login into e17
Seeded last month: Arch 50 gig, derivatives 1 gig
Desktop @3.3GHz 8 gig RAM, linux-ck
laptop #1 Atom 2 gig RAM, Arch linux stock i686 (6H w/ 6yrs old battery ) #2: ARM Tegra K1, 4 gig RAM, ChrOS
Atom Z520 2 gig RAM, OMV (Debian 7) kernel 3.16 bpo on SDHC | PGP Key: 0xFF0157D9
Offline
Yes, it can be ignored.
oldpond = glide
Offline