+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: PVR Development (/forumdisplay.php?fid=136)
+--- Thread: [VDR] "No PVR add-on enabled" popup when xbmc starts (/showthread.php?tid=117857)
Pages: 1 2
[VDR] "No PVR add-on enabled" popup when xbmc starts - ezechiel1917 - 2011-12-27 23:55
I'm running stable57 pulse ppa build with 1.7.21 vdr + vdr vnsiserver plugin (xbmc+vdr on same machine) and every time xbmc starts it popups dialogue "No PVR add-on enabled"
After clicking ok it loads PVR clients addon window where VDR VNSI addon is already enabled and also immediately loads Channels/EPG from VDR, PVR works just fine.
How can I get rid off this popup? I've tried deleting addons/epg/tv dbs, but that didn't help.
Thanks.
Code:
22:25:17 T:3012245312 INFO: skin loaded...
22:25:17 T:3012245312 NOTICE: Start - EPG thread started
22:25:17 T:2869173104 DEBUG: Thread EPG updater start, auto delete: 0
22:25:17 T:3012245312 NOTICE: PVRManager - starting up
22:25:17 T:2860780400 DEBUG: Thread PVR manager start, auto delete: 0
22:25:17 T:3012245312 DEBUG: Activating window ID: 12999
22:25:17 T:3012245312 DEBUG: ------ Window Init (Startup.xml) ------
22:25:17 T:3012245312 INFO: Loading skin file: Startup.xml
22:25:17 T:3012245312 INFO: initializing python engine.
22:25:17 T:2869173104 DEBUG: Thread EPG updater 2869173104 terminating
22:25:17 T:2869173104 DEBUG: Thread PVR add-on updater start, auto delete: 0
22:25:17 T:2869173104 DEBUG: InitialiseClient - initialising add-on 'VDR VNSI Client'
22:25:17 T:2869173104 DEBUG: PVR - Create - creating PVR add-on instance 'VDR VNSI Client'
22:25:17 T:2869173104 DEBUG: ADDON: Dll Initializing - VDR VNSI Client
22:25:17 T:2869173104 DEBUG: SECTION:LoadDLL(/usr/lib/xbmc/addons/pvr.vdr.vnsi/XBMC_VDR_vnsi.pvr)
22:25:17 T:2869173104 DEBUG: Loading: /usr/lib/xbmc/addons/pvr.vdr.vnsi/XBMC_VDR_vnsi.pvr
22:25:17 T:2869173104 DEBUG: AddOnLog: VDR VNSI Client: Creating VDR VNSI PVR-Client
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'host'
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'port'
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'priority'
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'convertchar'
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'timeout'
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'handlemessages'
22:25:17 T:2869173104 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR VNSI Client' requests setting 'autochannelgroups'
22:25:17 T:2869173104 ERROR: AddOnLog: VDR VNSI Client: Open - Can't connect to VSNI Server: Connection refused
22:25:17 T:2869173104 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
22:25:17 T:2869173104 INFO: Called Add-on status handler for '1' of clientName:VDR VNSI Client, clientID:pvr.vdr.vnsi (same Thread=no)
22:25:17 T:2869173104 ERROR: PVR - InitialiseClient - can't initialise add-on 'VDR VNSI Client'
22:25:17 T:2869173104 INFO: Loading skin file: DialogOK.xml
22:25:17 T:2992843632 DEBUG: Thread CAddonStatusHandler:pvr.vdr.vnsi start, auto delete: 1
22:25:17 T:2992843632 DEBUG: Thread CAddonStatusHandler:pvr.vdr.vnsi 2992843632 terminating (autodelete)- illiac4 - 2011-12-28 19:45
http://stmlabs.com/forum/topic/pvr-tvheadend-addon-error
- ant_thomas - 2011-12-30 20:06
Does this happen if you just restart XBMC? (rather than the system)
Could be XBMC starting before VDR has got initialized and fully started.
I have VDR running on a separate computer and I never get this issue. It takes a few seconds for XBMC to start loading the channels, but I get no popups usually.
I only get popups if VDR or the computer it is on has crashed. At which point starting restarting VDR sorts that and XBMC automatically picks up VDR.
The only difference is I'm using XVDR rather than VNSI.
- FernetMenta - 2011-12-30 20:51
Would you like to try this patch?
https://github.com/FernetMenta/xbmc/commit/9cdd0f348875bc4a65033187cc976bb2532b821b
- ezechiel1917 - 2011-12-31 13:41
illiac4 Wrote:http://stmlabs.com/forum/topic/pvr-tvheadend-addon-error
That doesn't seems related to my problem, everything is working just fine after clicking ok on the popup.
ant_thomas Wrote:Does this happen if you just restart XBMC? (rather than the system)
Could be XBMC starting before VDR has got initialized and fully started.
I have VDR running on a separate computer and I never get this issue. It takes a few seconds for XBMC to start loading the channels, but I get no popups usually.
I only get popups if VDR or the computer it is on has crashed. At which point starting restarting VDR sorts that and XBMC automatically picks up VDR.
The only difference is I'm using XVDR rather than VNSI.
I got the same popup with XVDR when I tried it. I exactly thought it could be because XBMC starts before VDR, but I get VDR checking for plugins message just before XBMC logo appears, so not sure this is the case. I'm not sure how to restart xbmc (never got it working locally somehow) and not sure how can I properly restart via ssh with uxlaunch in the process now. Also this popup is not shown after system resumes from suspend, only background message that Connection to VDR server restored (That's with vdr stop on suspend and vdr start on resume)
EDIT: No popup, when xbmc crashes and automatically restarts itself.
FernetMenta Wrote:Would you like to try this patch?
https://github.com/FernetMenta/xbmc/commit/9cdd0f348875bc4a65033187cc976bb2532b821b
Thanks, but unfortunately I won't be able to test it on this system now, I'll have a look at it again when I have more time to manually compile your version.
- ant_thomas - 2011-12-31 14:30
I'm no expert but that looks like XBMC starting before VDR is fully initialized. Is it possible to put a "sleep 5" maybe in the XBMC startup script.
- opdenkamp - 2011-12-31 15:56
the problem is probably caused by a bug in pvr/addons/PVRClients.cpp
if there's no report on github about this issue yet, please create one.
- ezechiel1917 - 2012-01-01 22:00
ant_thomas Wrote:I'm no expert but that looks like XBMC starting before VDR is fully initialized. Is it possible to put a "sleep 5" maybe in the XBMC startup script.
I don't think this is the real cause of this issue, message concretely says "No PVR add-on enabled" while I have PVR addon already enabled. IMO it should not matter if the backend is or is not available with this kind of message. I would understand if there was an error with different statement (No PVR backend reachable or something like that), but "No PVR add-on enabled" simply means user has xbmc set to Enable PVR but didn't enable any addons yet, which is not this case.
I'll report this on GIT as dushmaniac suggested.
- ant_thomas - 2012-01-02 00:17
ezechiel1917 Wrote:I don't think this is the real cause of this issue, message concretely says "No PVR add-on enabled" while I have PVR addon already enabled. IMO it should not matter if the backend is or is not available with this kind of message. I would understand if there was an error with different statement (No PVR backend reachable or something like that), but "No PVR add-on enabled" simply means user has xbmc set to Enable PVR but didn't enable any addons yet, which is not this case.
I'll report this on GIT as dushmaniac suggested.
Have you given it a go though?
Since you said
Quote:EDIT: No popup, when xbmc crashes and automatically restarts itself.
Which to me says that if XBMC is started/restarted after a while/delay then it manages to connect to VDR without any issues.
- cavej03 - 2012-01-02 04:54
I have to agree with ant_thomas, I had the same problem with tvheadend, although make it sleep for like 1 min or more that way you can be sure vdr has started.. (Just to start of with)
We can make a better script that simply waits for vdr to start before xbmc later