[gelöst] "start kodi" nach update

BooStar · 30. Januar 2016

Hallo zusammen,
ich habe soeben ein apt-get update && apt-get dist-upgrade geamacht,
jetzt startet Kodi leider nicht mehr, normalerweise start ich Kodi mit: stop vdr-frontend && start kodi
Aktuell wird aber nur das frontend gestoppt, kodi kommt aber nicht hoch...

Jemand eine Idee wo ich hier ansetzen kann?

/edit: das kodi.log wird nicht erstellt und das syslog ist unauffällig...
/edit2: Das Problem hatte nichts mit dem update zu tun, sondern viel mehr mit Netzwerkproblemen... siehe unten

seahawk1986 · 30. Januar 2016

Was steht denn in /var/log/upstart/kodi.log ? Mit dem Stand aus testing kann ich hier keinen Fehler entdecken.

BooStar · 30. Januar 2016

Moin seahawk,
danke für die schnelle Rückmeldung:

Code

method return sender=:1.130 -> dest=:1.140 reply_serial=2
   int32 250
   string "Remote control disabled"
written backup for HDMI-0 to /var/lib/vdr/.kodi/.display_cache/HDMI-0-videodevice.xml
PICTURE::LoadImageFromMemory: Unable to decode image. Error:Decode: Unknown or wrong format
PICTURE::LoadImageFromMemory: Unable to decode image. Error:Decode: Unknown or wrong format
PICTURE::LoadImageFromMemory: Unable to decode image. Error:Decode: Unknown or wrong format
PICTURE::LoadImageFromMemory: Unable to decode image. Error:Decode: Unknown or wrong format
Sending action: Quit
method return sender=:1.130 -> dest=:1.150 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.130 -> dest=:1.155 reply_serial=2
   int32 250
   string "Remote control disabled"
written backup for HDMI-0 to /var/lib/vdr/.kodi/.display_cache/HDMI-0-videodevice.xml
Sending action: Quit
method return sender=:1.130 -> dest=:1.160 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.130 -> dest=:1.167 reply_serial=2
   int32 250
   string "Remote control disabled"
written backup for HDMI-0 to /var/lib/vdr/.kodi/.display_cache/HDMI-0-videodevice.xml
Sending action: Quit
method return sender=:1.130 -> dest=:1.177 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.130 -> dest=:1.186 reply_serial=2
   int32 250
   string "Remote control disabled"
written backup for HDMI-0 to /var/lib/vdr/.kodi/.display_cache/HDMI-0-videodevice.xml
Sending action: Quit
method return sender=:1.130 -> dest=:1.191 reply_serial=2
   int32 250
   string "Remote control enabled"
method return sender=:1.57 -> dest=:1.73 reply_serial=2
   int32 250
   string "Remote control enabled"
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
written backup for HDMI-0 to /var/lib/vdr/.kodi/.display_cache/HDMI-0-videodevice.xml
Sending action: Quit
Exception SystemExit in <function _remove at 0x7fac880a57d0> ignored
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
Can't open display :1
Traceback (most recent call last):
  File "/usr/bin/set-kodi-display", line 68, in <module>
    output = get_output_names()[0]
  File "/usr/bin/set-kodi-display", line 23, in get_output_names
    env={"DISPLAY": os.environ["DISPLAY"]}
  File "/usr/lib/python3.4/subprocess.py", line 620, in check_output
    raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command '['xrandr']' returned non-zero exit status 1
/proc/self/fd/9: line 17:  2515 Killed                  sleep 1
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
method return sender=:1.54 -> dest=:1.60 reply_serial=2
   int32 250
   string "Remote control enabled"
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
Can't open display :1
Traceback (most recent call last):
  File "/usr/bin/set-kodi-display", line 68, in <module>
    output = get_output_names()[0]
  File "/usr/bin/set-kodi-display", line 23, in get_output_names
    env={"DISPLAY": os.environ["DISPLAY"]}
  File "/usr/lib/python3.4/subprocess.py", line 620, in check_output
    raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command '['xrandr']' returned non-zero exit status 1
/proc/self/fd/9: line 17:  2871 Killed                  sleep 1
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
method return sender=:1.7 -> dest=:1.57 reply_serial=2
   int32 250
   string "Remote control disabled"
/var/lib/vdr/.kodi/userdata/guisettings.xml not found, creating stub file
written backup for Default to /var/lib/vdr/.kodi/.display_cache/Default-videodevice.xml
/var/lib/vdr/.kodi/.display_cache/HDMI-0-videodevice.xml not found, creating stub file
Sending action: Quit
method return sender=:1.7 -> dest=:1.62 reply_serial=2
   int32 250
   string "Remote control enabled"
root@yavdr01:/var/lib/vdr/.kodi/temp#

Alles anzeigen

seahawk1986 · 30. Januar 2016

Zitat von BooStar

Can't open display :1

Ohne laufenden X-Server dürfte das etwas schwer sein KODI zu starten - hast du da vorher etwas verbastelt oder gestoppt?

BooStar · 30. Januar 2016

Ich probiers nochmal... Moment...
Also nach einen reboot startet der vdr ganz normal, dann ein stop vdr-frontend klappt auch noch,
und nach einem "start kodi":

Code

Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files
Can't open display :1
Traceback (most recent call last):
  File "/usr/bin/set-kodi-display", line 68, in <module>
    output = get_output_names()[0]
  File "/usr/bin/set-kodi-display", line 23, in get_output_names
    env={"DISPLAY": os.environ["DISPLAY"]}
  File "/usr/lib/python3.4/subprocess.py", line 620, in check_output
    raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command '['xrandr']' returned non-zero exit status 1
/proc/self/fd/9: line 17:  2806 Killed                  sleep 1
Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files

Alles anzeigen

seahawk1986 · 30. Januar 2016

Zitat von BooStar

Code

Error org.freedesktop.DBus.Error.ServiceUnknown: The name de.tvdr.vdr was not provided by any .service files

Die Meldung kommt, wenn der VDR mit dbus2vdr-Plugin nicht läuft. Was liefert denn bei dir

Code

export DISPLAY=:1
xrandr

BooStar · 30. Januar 2016

Hmm nix...
//edit:sorry

Code

root@yavdr01:~# export DISPLAY=:1
root@yavdr01:~#

Code

root@yavdr01:~# xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1020mm x 570mm
   1920x1080      60.0 +   59.9     59.9     50.0*    30.0     25.0     24.0     60.1     60.0     50.0
   1920x1200      60.0
   1680x1050      69.9     60.0     59.9
   1600x1200      65.0     60.0
   1600x900       60.0
   1440x900       59.9
   1400x1050      74.8     70.0     60.0
   1366x768       59.8
   1360x768       60.0     59.8
   1280x1024      75.0     60.0
   1280x960       60.0
   1280x800       59.8
   1280x720       60.0     59.9     50.0
   1152x864       75.0     75.0     70.0     60.0
   1024x768       75.0     70.1     60.0
   960x600        60.0
   960x540        60.0
   840x525        69.9     60.0     59.9
   832x624        74.6
   800x600        75.0     72.2     60.3     56.2
   720x576        50.0     50.1
   720x480        59.9     60.1
   720x450        59.9
   700x525        74.8     60.0
   680x384        60.0     59.8
   640x480        75.0     72.8     72.8     59.9
   512x384        70.1     60.0
   400x300        72.2
   320x240        72.8     60.1
root@yavdr01:~#

Alles anzeigen

BooStar · 30. Januar 2016

Ok.. geht wieder ... kodi wollte wohl starten, konnte aber nicht, weil es den DatenbankServer nicht erreichen konnte...
Danke für die Hilfe...

seahawk1986 · 30. Januar 2016

Und der Aufruf von xrandr klappt auch noch nach einem stop vdr-frontend?

BooStar · 30. Januar 2016

Hmm nee..

Code

root@yavdr01:~# xrandr
Can't open display

Aber wie gesagt.. jetzt tut wieder alles....

seahawk1986 · 30. Januar 2016

Das ist aber trotzdem komisch, der X-Server sollte bei einem stop vdr-frontend ja eigentlich noch laufen

BooStar · 30. Januar 2016

Sorry für die Verwirrung... ich muss erst das Display exportieren, oder?

Klappt:

Code

root@yavdr01:~# stop vdr-frontend
vdr-frontend stop/waiting
root@yavdr01:~# export DISPLAY=:1
root@yavdr01:~# xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1020mm x 570mm
   1920x1080      60.0 +   59.9     59.9     50.0*    30.0     25.0     24.0     60.1     60.0     50.0
   1920x1200      60.0
   1680x1050      69.9     60.0     59.9
   1600x1200      65.0     60.0
   1600x900       60.0
   1440x900       59.9
   1400x1050      74.8     70.0     60.0
   1366x768       59.8
   1360x768       60.0     59.8
   1280x1024      75.0     60.0
   1280x960       60.0
   1280x800       59.8
   1280x720       60.0     59.9     50.0
   1152x864       75.0     75.0     70.0     60.0
   1024x768       75.0     70.1     60.0
   960x600        60.0
   960x540        60.0
   840x525        69.9     60.0     59.9
   832x624        74.6
   800x600        75.0     72.2     60.3     56.2
   720x576        50.0     50.1
   720x480        59.9     60.1
   720x450        59.9
   700x525        74.8     60.0
   680x384        60.0     59.8
   640x480        75.0     72.8     72.8     59.9
   512x384        70.1     60.0
   400x300        72.2
   320x240        72.8     60.1
root@yavdr01:~#

Alles anzeigen

seahawk1986 · 30. Januar 2016

Zitat von BooStar

Sorry für die Verwirrung... ich muss erst das Display exportieren, oder?

Ja, sonst weiß er in der SSH-Sitzung nicht, welchen Bildschirm er nehmen soll.

[gelöst] "start kodi" nach update

Jetzt mitmachen!

Teilen