search

i96751414 / plugin.video.torrest

Torrest plugin for Kodi
MIT License
27 stars 6 forks source link

Torrest deamon not initialized, most probably due to a "&" in the Torrest add-on path #8

Closed lopezvg closed 3 years ago

lopezvg commented 3 years ago

2021-03-09 16:10:13.765 T:9228 NOTICE: [plugin.video.torrest] Daemon not found. Aborting service... 2021-03-09 16:10:20.790 T:8756 ERROR: [plugin.video.torrest] Failed to update background progress repeats 3 more times 2021-03-09 16:10:48.287 T:7920 ERROR: [plugin.video.torrest] Caught exception: Traceback (most recent call last): File "C:\Users\Tere&Luis\AppData\Roaming\Kodi\addons\plugin.video.torrest\lib\navigation.py", line 435, in run plugin.run() File "C:\Users\Tere&Luis\AppData\Roaming\Kodi\addons\script.module.routing\lib\routing.py", line 130, in run self._dispatch(self.path) File "C:\Users\Tere&Luis\AppData\Roaming\Kodi\addons\script.module.routing\lib\routing.py", line 141, in _dispatch view_func(**kwargs) File "C:\Users\Tere&Luis\AppData\Roaming\Kodi\addons\plugin.video.torrest\lib\navigation.py", line 52, in wrapper raise e IOError: [Errno 2] No such file or directory: u'C:/Users/Tere'

i96751414 commented 3 years ago

I wasn't able to reproduce this, and I tested both Kodi 18/19. The '&' should not be a problem in the latest version.

I'll need more info to understand what's happening here. A full log would be appreciated.

Also, please make sure the correct addon (containing the binaries) was installed.

lopezvg commented 3 years ago

No problem LOG885986347.log

The version is the latest. If the user followed the rules the binary should be correct, but I have way to verify it.

Please find at the end of the log a summary of the status of the Kodi installation

i96751414 commented 3 years ago

Also, I've just remembered one thing, when calling 'play_path' route, the path must be url encoded. Probably that's why the '&' is breaking things here.

i96751414 commented 3 years ago

I'm closing this issue as I believe it is related with two external problems:

  1. The user didn't have the correct add-on installed (containing the binary);
  2. This was probably called from plugin://plugin.video.torrest/play_path?path=<path> and the path was not url encoded, so any & characters would break this.

Feel free to reopen it if that's not the case.

lopezvg commented 3 years ago

You were right in both cases: