[Milhouse]

Addons - Install from Zipfile isn't working for me. Nothing happens when I Select it but the other options (Install from Repo, My Addons) all work.

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

Incidentally, is there anything I can do to stop the "DEBUG: NFS:" messages appearing in the log, as they're so numerous it makes it difficult to see the important events?

You could always use

Code:

tail -f kodi.log | grep -v "DEBUG: NFS:"

as that will filter out those messages.

However your NFS configuration is the reason the context refresh messages are spamming the log.

For instance:

Code:

05:28:34.586 T:1604920224   DEBUG: NFS: Refreshing context for 192.168.1.64/Media, old: 9042, new: 11845
05:28:34.586 T:1604920224   DEBUG: NFS: Using cached context.
05:28:34.700 T:1604920224   DEBUG: NFS: Refreshing context for 192.168.1.64/Torrents, old: 9063, new: 11959
05:28:34.700 T:1604920224   DEBUG: NFS: Using cached context.
05:28:35.219 T:1697194912   DEBUG: NFS: Refreshing context for 192.168.1.64/Media, old: 11845, new: 12478
05:28:35.220 T:1697194912   DEBUG: NFS: Using cached context.
05:28:35.965 T:1487287200   DEBUG: NFS: Refreshing context for 192.168.1.64/Torrents, old: 11959, new: 13223
05:28:35.965 T:1487287200   DEBUG: NFS: Using cached context.

and then the above repeats a *lot*.

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.