2018-01-11, 03:03
After installing a new build of kodi 18 I am no longer able to open clientspecific settings in pvr & tv section. It seems liks kodi is totally unresponsive when selecting the entry. Settings have remained unchanged and vdr/kodi is running smoothly as before. Just that I can't access the vdr osd and settings any more.
vdr 2.3.8 is installed locally with currently only vnisserver and ddci2 plugin active
When selecting the menu entry only these lines are added to syslog:
Edit:
It's interesting, though, that when I open the clientspecific settings menu from another vnsi client (RPI3 running kodi 17.6/LE 8.2.2) which accesses the same vdr on the above host, I am getting the osd and settings displayed correctly and syslog shows:
vdr 2.3.8 is installed locally with currently only vnisserver and ddci2 plugin active
When selecting the menu entry only these lines are added to syslog:
Quote:Jan 11 01:17:11 kodi-mc vdr: [1240] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.confIs this a known issue wth the recent code or what else can I do to help troubleshoot?
Jan 11 01:17:11 kodi-mc vdr: [1240] VNSI: Client with ID 31 connected: 127.0.0.1:36136
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI Client 31->127.0.0.1:36136 thread started (pid=933, tid=1992, prio=high)
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI: Welcome client 'XBMC osd client' with protocol version '12'
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI: cxSocket::read(fd=24): eof, connection closed
Jan 11 01:17:11 kodi-mc vdr: [1992] VNSI Client 31->127.0.0.1:36136 thread ended (pid=933, tid=1992)
Jan 11 01:17:11 kodi-mc vdr: [1244] VNSI: Client with ID 31 seems to be disconnected, removing from client list
Edit:
It's interesting, though, that when I open the clientspecific settings menu from another vnsi client (RPI3 running kodi 17.6/LE 8.2.2) which accesses the same vdr on the above host, I am getting the osd and settings displayed correctly and syslog shows:
Quote:Jan 11 02:08:14 kodi-mc vdr: [1239] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.confSo to me it looks like the issue is only present in the new kodi 18 code. With previous kodi 18 alpha code, like from a week ago, I am pretty sure it was also still working.
Jan 11 02:08:14 kodi-mc vdr: [1239] VNSI: Client with ID 27 connected: 192.168.178.15:55962
Jan 11 02:08:14 kodi-mc vdr: [2533] VNSI Client 27->192.168.178.15:55962 thread started (pid=848, tid=2533, prio=high)
Jan 11 02:08:14 kodi-mc vdr: [2533] VNSI: Welcome client 'XBMC osd client' with protocol version '10'
Jan 11 02:08:14 kodi-mc vdr: [2533] VNSI: new osd provider