2017-04-10, 00:14
(2016-11-27, 00:23)mattlach Wrote:(2016-11-27, 00:02)mattlach Wrote:(2016-11-26, 23:53)mattlach Wrote: Hmm.
I've had this up and running using 16.04 and this guide since the June or so. Has been working beautifully, but I just ran into a problem today.
I had been lazy and not updated the Kodi box for a while, so I did a full update using apt-get (which installed a TON of stuff).
Upon reboot I'm faced with a graphical login screen and an error message "Unable to start session".
Does anyone know what might have been wrong? I'm thinking something in the update might have overwritten one of the config files? (though I was never prompted for this)
I appreciate any suggestions.
Thanks,
Matt
I think I found the problem.
Something in the update changed the /etc/systemd/system/display-manager.service symlink to point to /lib/systemd/system/lightdm.service instead of the /etc/systemd/system/kodi.service as shown in the guide.
Going to reset the symlink back to the where it is in the guide, reboot and see if this fixes it.
Yep, that solved it.
Not sure why this symlink was overwritten but some update did it on all three of my HTPC's.
Luckily it is easy to fix, if anyone else has the problem.
1.) Either SSH in or locally do CTRL-ALT-F1 to go to first text console
2.) Log in using your credentials
3.) issue following command
Code:sudo ln -sf /etc/systemd/system/kodi.service /etc/systemd/system/display-manager.service
Note the added "f", this means "force" and overwrites the incorrect symlink.
4.) Reboot.
After this you should be back in business.
This just happened to me again.
Has anyone else had this happen?
I'm considering adding a entry to my crontab that overwrites this symlink every 15 minutes or so so I don't have to do this again.