Posts: 17,859
Joined: Jul 2011
Reputation:
371
if you mean kodi nightlies a fix is in the works
Posts: 7,648
Joined: Jun 2011
Reputation:
287
this should be fixed in tomorrows nightly.
in the mean time start kodi like this:
KODI_HOME=/usr/share/kodi/ kodi
Posts: 21
Joined: Oct 2010
Reputation:
0
Hello, I've a minimal installation where Kodi is launched by a systemd service:
[Unit]
Description = Kodi Media Center
After = systemd-user-sessions.service sound.target
[Service]
User = kodi
Group = kodi
Type = simple
PAMName = login
ExecStart = /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
Restart = on-abort
RestartSec = 5
[Install]
WantedBy = multi-user.target
how can I adapt your workround?
Thanks in advance
Posts: 21
Joined: Oct 2010
Reputation:
0
found a solution:
export KODI_HOME=/usr/share/kodi/
then
xinit kodi
Thanks
Posts: 1
Joined: Sep 2016
Reputation:
0
I too have had a similar experience with the new Kubuntu release and please note I have multiple drives in my box. I was just about ready to give up when I stumbled upon this temporary fix. Hope this helps...
We have Kodi and the O/S on separate drives, music files on another, movie files on yet another, ect. Kodi appeared to be lost and could not find what it needed leaving the program non-op. I found if I opened the file manager (Dolphin) to the desired drives for Kodi; Example: the required use files and media. The Kodi program can then easily find the needed path. For now I simply open the File manager to all my needed drives, shrink Dolphin down to the bottom of the page and run Kodi full screen. Not sure if this is your exact situation but perhaps this temporary fix helps someone.
Hoping this work around will be resolved soon.
Posts: 7,648
Joined: Jun 2011
Reputation:
287
thats got nothing to do with the OPs issue, which has been fixed almost 2 months ago.
If you have kodi installed on drives not mounted at boot, it's obvious that kodi cannot start.