(2017-04-27 08:09)Milhouse Wrote: The "Install from Zip file" home screen widget has never worked.
If you want to install from a zip file, use Addons > Add-on browser > Install from zip file
Thanks, that did the trick.
I'm still not having any luck with TVheadend using #426 with your TVheadend build #426 though. lsusb shows my tuner is recognised
Bus 001 Device 005: ID 1b80:e409 Afatech IT9137FN Dual DVB-T [KWorld UB499-2T]
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 046e:5577 Behavior Tech. Computer Corp.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
but no tuners are listed in the browser GUI (http://192.168.1.85:9981
) under Configuration - DVB Inputs - TV Adapters.
There's some errors in the log about TVheadend Client but I don't think they matter at the moment, it's the service I'm having problems with.
Quote:It looks like you have two NFS shares, and Kodi maintains only a single NFS context. When you're requesting information from Media and then from Torrents, and then again from Media, and then again from Torrents, Kodi is continually having to refresh it's single NFS context (which then spams the debug log).
Perhaps if you had a single NFS export, eg. 192.168.1.64/share, and then within your "share" export you have Media and Torrents directories, so that Kodi can access all of the content via a single NFS context.
However I don't really know if refreshing the NFS contexts is a particularly "expensive" (time consuming) process, so it may not be worthwhile and you'll just have to put up with the debug log spam.
Ah, OK. I'll limit it to one NFS share then. Even if it's not causing any resource issues, I'd like to stop the log spam occurring.