+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: PVR & Live TV Support (https://forum.kodi.tv/forumdisplay.php?fid=167)
+---- Forum: VDR (https://forum.kodi.tv/forumdisplay.php?fid=169)
+---- Thread: v18 unable to open clientspecific settings after update (/showthread.php?tid=326906)
unable to open clientspecific settings after update - Spirou - 2018-01-11
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:
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
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
I am not ware of any issues and here all works as expected. What build do you use? Please post a debug log
RE: unable to open clientspecific settings after update - Spirou - 2018-01-11
Debug log is available from https://paste.ubuntu.com/26364955/
Matching syslog entries at 09:58.30:
Quote:Jan 11 09:58:30 kodi-mc vdr: [1223] loading /var/lib/vdr/plugins/vnsiserver/allowed_hosts.confI pressed volume up before und volume down after I tried to open client specific settings from gui -maybe that helps to locate the respective entries in the log.
Jan 11 09:58:30 kodi-mc vdr: [1223] VNSI: Client with ID 2 connected: 127.0.0.1:47304
Jan 11 09:58:30 kodi-mc vdr: [1773] VNSI Client 2->127.0.0.1:47304 thread started (pid=886, tid=1773, prio=high)
Jan 11 09:58:30 kodi-mc vdr: [1773] VNSI: Welcome client 'XBMC osd client' with protocol version '12'
Jan 11 09:58:30 kodi-mc vdr: [1773] VNSI: cxSocket::read(fd=18): eof, connection closed
Jan 11 09:58:30 kodi-mc vdr: [1773] VNSI Client 2->127.0.0.1:47304 thread ended (pid=886, tid=1773)
Jan 11 09:58:30 kodi-mc vdr: [1226] VNSI: Client with ID 2 seems to be disconnected, removing from client list
System info tells me I'm running on version "Kodi 18.0-ALPHA1 Git:20180110-f638e40-dirty"
System is Ubuntu 16.04.3 LTS (GNU/Linux 4.13.0-26-generic x86_64) running only VDR 2.3.8 and kodi 18 alpha.
Thanks for looking into it.
Edit:
Here's another debug log with less noise (after startting with an empty .kodi folder and enabling only vdr vnsi client addon:
https://paste.ubuntu.com/26365053/
Yet, still the same issue
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
Where did you get Kodi and the vnsi addon from?
RE: unable to open clientspecific settings after update - Spirou - 2018-01-11
Checked out the sources from github (git clone git://github.com/xbmc/xbmc.git kodi) and followed the instructions in docs/README.ubuntu and docs/README.linux on how to compile.
Edit: One thing I noticed was that ubuntu kernel was updated from 4.10 to 4.13 last night (before checkout and compile of latest code). Not sure if this has any impact.
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
How did you build vnsi? Can you post the build output?
RE: unable to open clientspecific settings after update - Spirou - 2018-01-11
I uploaded the content of tools/depends/target/binary-addons/native/pvr.vdr.vnsi-prefix/src/pvr.vdr.vnsi-build/CMakeFiles/CMakeOutput.log to http://paste.ubuntu.com/26365825/. Hope this is what you require. Else, please let me know which file/info to upload.
For the actual build of vnsi addon, after build of kodi I proceeded with make -C tools/depends/target/binary-addons PREFIX=/usr/local as per the instructions given in README.linux.
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
I am more interested in the compiler output. Looking for an entry like this: "VDR OSD support enabled via OpenGL" and "Configured render system:"
RE: unable to open clientspecific settings after update - Spirou - 2018-01-11
Do you have any hint where to find that output? I used a grep -R "Configured render system:" in the source directory but didn't find anything. Looks like all output was just sent to the console.
I could rebuild kodi and or vnsi with sources checked out yesterday if you could guide me on how to log properly and clean up prior to re-build - usually I remove old directory before checking out fresh code from github to avoid interference with old files.
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
(2018-01-11, 14:48)Spirou Wrote: Do you have any hint where to find that output? I used a grep -R "Configured render system:" in the source directory but didn't find anything. Looks like all output was just sent to the console.Yes, it is written to the console. You can direct console output to a file by adding > somefile.txt to the command
RE: unable to open clientspecific settings after update - Spirou - 2018-01-11
Here you go: http://paste.ubuntu.com/26366297/
I tried a re-build via make -C tools/depends/target/binary-addons PREFIX=/usr/local ADDONS="pvr.vdr.vnsi" clean && make -C tools/depends/target/binary-addons PREFIX=/usr/local ADDONS="pvr.vdr.vnsi"
The relevant lines in the output read like:
Quote:-- VDR OSD support enabled via OpenGL
-- Configured render system: gl
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
looks all good. does music visualization spectrum work on your system?
RE: unable to open clientspecific settings after update - FernetMenta - 2018-01-11
should be fixed now: vnsi 3.5.2
RE: unable to open clientspecific settings after update - Spirou - 2018-01-11
Wow, that was quick. Thanks for fixing.
However, since you were asking: I enabled music virtualization spectrum but it doesn't seem to produce any output either.
Will check out latest code later and rebuild kodi and addons from scratch.
Update:
Your fix really made my day
I'm able to access the client specific settings again.Many thanks again!
Out of curiosity I applied your fix to visualization.spectrum/resources/shaders/1.2/frag.glsl - and voila! It's working again
Are you going to commit this fix also to the visualization.spectrum addon or do I need to raise a request in another thread?