2019-02-12, 17:16
No i am not running Kodi on windows. I only use libreelec on my raspi 3 (as a client).
My server is a win 7 machine running hanewin nfs server app.
My server is a win 7 machine running hanewin nfs server app.
(2019-02-11, 20:29)AnonTester Wrote: This is on Linux (Ubuntu 18.04.1 LTS) with Kodi 18.1-RC1 Git:20190211-1c60cbdJust to confirm, version 1.0.7 fixes both the error message in movie.py line 204 and the issue with the remote path on nfs. Thank you!
(2019-02-12, 17:12)jvandenbroek Wrote:It 's ok no problem with it. Truth is that my windows nfs app is rather old (i haven't updated to last version for a long time now cause it needs a license) so..maybe this has been fixed with latest releases.(2019-02-12, 17:05)Haris1977 Wrote: Ok, here is my /storage/.kodi/temp/kodi.log file (with new zip addon)Thanks, this helps. It indeed doesn't detect any files left (no file named after =), but it does count one. I need to figure out if this has to do with using nfs:// (and/or smb://) paths, or something Windows related. I assume you're running Kodi also on Windows, correct? Not just the file server.
https://www118.zippyshare.com/v/rgYsUj0l/file.html
Edit: Hmm guess that's not the case, seems like you're using LibreELEC looking at the reported version in your log. Will need to setup a similar setup here and test it with nfs:// paths. Guess that call will just always return an empty item, regardless whether any files are left. To be continued
Edit 2: I've just tested it on LibreELEC with a test library located at nfs://, just like your setup, with only 1 set of files in it (mkv, jpg etc named the same). This does work as expected here, removes the empty directory and reports 0 left over files. So it seems specific to your setup since it reports 1 file left over, it's just really unclear to me why that would be. Maybe the used NFS server (mine is just standard Linux, yours is kind a 'exotic' ) does report something different back to the client, which Kodi stores as an empty file name. So I don't think there is much I can do at this point, unless we know why that empty file name is reported back (that would require packet inspection with something like Wireshark, but it's not worth the effort if you're not familiar with it).
(2019-02-19, 15:22)Haris1977 Wrote: It seems that this add-on can not auto-delete a specific *.mp4 file that i have (i get no notification at all).
The file is uploaded here (if y want to take a look at it):
https://www75.zippyshare.com/v/8DVtq0Ej/file.html
(2019-02-19, 18:39)jvandenbroek Wrote:Oups..I see there is a new update (1.0.8). This one fixes all of my problems ! Now i get the "pop-up" notification to delete my file (mentioned in post #276) as long as the last empty remaining folder!(2019-02-19, 15:22)Haris1977 Wrote: It seems that this add-on can not auto-delete a specific *.mp4 file that i have (i get no notification at all).
The file is uploaded here (if y want to take a look at it):
https://www75.zippyshare.com/v/8DVtq0Ej/file.html
I've checked it out, no problems here on a local path. Maybe some other add-on is preventing it to finish properly, you could try it again after restarting Kodi. If the issue remain, please post a debug log.
(2019-06-23, 21:41)AnonTester Wrote: Kodi 19 deprecated old strings.xml language resource files which broke AfterWatch completely. I converted the language resources to the .po format, fixed the issue with the alternative move function and bumped the version to 1.0.9.
You can install it from my repository https://github.com/AnonTester/kodi-repo/...-1.0.0.zip or get it from https://github.com/AnonTester/kodi-repo/...afterwatch