Bug#854985: kodi.service spamming the logs due to xinit being missing

[Bálint Réczey]

Control: severity -1 serious
Control: tags -1 confirmed

Hi Gabor,

2017-02-12 22:24 GMT+01:00 Gábor <gombasg at digikabel.hu>:
> Package: kodi
> Version: 2:17.0+dfsg1-2
> Severity: normal
>
> Dear Maintainer,
>
> Since the latest round of updates, kodi.service spams syslog with:
>
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Service hold-off time over, scheduling restart.
> Feb 12 22:14:35 zephyr systemd[1]: Stopped Kodi Open Source Home Theatre.
> Feb 12 22:14:35 zephyr systemd[1]: Started Kodi Open Source Home Theatre.
> Feb 12 22:14:35 zephyr systemd[17588]: kodi.service: Failed at step USER spawning /usr/bin/xinit: No such process
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Main process exited, code=exited, status=217/USER
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Unit entered failed state.
> Feb 12 22:14:35 zephyr systemd[1]: kodi.service: Failed with result 'exit-code'.
>
> If Kodi really needs xinit, then the package should depend on it. xinit
> is rather old-fashioned, and is no longer generally useful if one runs
> one of the "big" desktop environments, so nothing should assume it just
> exists.
>
> Actually, I don't think this service should be automatically enabled at
> all. I do not want to run kodi in stand-alone mode.

Yes, this is indeed the problem.
I'll disable it by default in the next upload.

Thanks,
Balint