I have enable Yarss in preferences but there is no menu for Yarss. Any idea why? or Did I miss something?

[Chris Fiel]

‌

[Bendik]

Version of Deluge? Are you running thin client mode? Which version of Yarss2?

[Justin Hardage]

I’m having this same issue.

Client:

• Windows 10
• Deluge 2.1.1 Thin Client

Server:

• Synology NAS DSM 7.1.1-42962 Update 6
• Docker 20.10.3-1308
• Container binhex / arch-delugevpn release 2.1.1-4-02

Inside container:

deluge --version
deluge 2.1.1
libtorrent: 2.0.9.0
Python: 3.11.3
OS: Linux Arch Linux

‌

egg version:

• YaRSS2-2.1.5-py3.10.egg

‌

Initially, I wasn’t able to activate the YaRSS plugin, because of the python version mismatch, but simply renaming it to YaRSS2-2.1.5-py3.11.egg allowed me to enable it in Preferences in the desktop thin client.

However, the YaRSS2 menu still does not appear in Preferences. I previously used it successfully with an earlier version of the binhex / arch-delugevpn container, but I had to update my version of Deluge to work with certain trackers. The latest version of arch-delugevpn comes with Python 3.11, so I’m hoping to get this going with that version instead of rolling back.

‌

[Justin Hardage]

Further datapoint:
Deluge picked up my RSS feeds and started downloading them again, despite me not being able to get to the menu. So it’s definitely in there and working even though I can’t interact with it

[Bendik]

Can you start deluge with logging enabled and see if there are errors reported?

[Bendik]

This could be linked to Issue 74 which I believe is caused by deluge not bundling chardet library

[Justin Hardage]

It looks like it was another case of needing to rename the egg, but it was a bit surprising. Here are my steps:

1. Manually download the egg
2. Change its filename from YaRSS2-2.1.5-py3.10.egg to YaRSS2-2.1.5-py3.11.egg, to match my Docker container’s Python version

3. Put the 3.11 server egg inside the docker container.

   1. SSH into server
   2. docker exec -it <image_name> bash
   3. Copy file into ~/.config/deluge/plugins

4. Remove YaRSS egg files from client machine folders

   • C:\\Users\\Username\\AppData\\Roaming\\deluge\\plugins and
   • C:\\Program Files\\Deluge\\deluge\\plugins

5. Install new YaRSS2 egg from client Preferences → Plugins

6. Locate the newly installed egg: C:\\Users\\Username\\AppData\\Roaming\\deluge\\plugins

7. Check Python version on client with C:\\Program Files\\Deluge\\deluge.exe --version

   1. deluge 2.1.1
      libtorrent: 1.2.15.0
      Python: 3.9.13
      OS: Windows 10 10.0.19044 SP0 Multiprocessor Free

8. Rename the client egg from YaRSS2-2.1.5-py3.10.egg to YaRSS2-2.1.5-py3.9.egg

   1. Yes, it’s a different Python version than the server. Yes, the client automatically picked a version it couldn’t use. No, I don’t know why

9. Enable YaRSS2 in Preferences → Plugins; restart Deluge client.

‌

Thanks for checking on this issue anyway!

[Laszlo Szilagyi]

I have the same issue on my Synology NAS. I’m using Deluge:

Client: 2.1.1.dev61
Server: 2.1.1.dev61
libtorrent: 2.0.9.0 and Python 3.11.

I also did the renaming trick which made the checkbox to appear in the Plugins menu, but no new menu for the YaRSS itself.

‌