bro wrote:
If you are able to run Deluge in a debugger it might be possible to find the cause.
Unfortunately I don't have the knowledge on how to go about this. If this is a fringe case and hasn't been reported before we can assume it's due to my configuration and in which case, I won't persue any further. Thanks for the consideration, but I'd rather not waste your time.
Crashes have been reported before, but I thought those issues had been sorted out i the later versions. Such crashes due to external libraries can be notoriously hard to figure out, at least when there is no useful debug info.
To debug I believe you'll need a python enabled GDB build. I haven't tried to debug a python program with GDB on Windows, but I expect it's just crap.
However, the problem is most probably in the GUI part so if you run deluge in thin client mode you should be able to have the daemon running without crashing.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
@ANOka, sorry, I remembered wrong on how the cookies were matched.
In the RSS Feeds tab you will see the base url in the "Site" column for each RSS Feed. It will match this value against the value in the cookies settings, so make sure the value in the cookie settings equals the one in the "Site" column.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
bro wrote:@ANOka, sorry, I remembered wrong on how the cookies were matched.
In the RSS Feeds tab you will see the base url in the "Site" column for each RSS Feed. It will match this value against the value in the cookies settings, so make sure the value in the cookie settings equals the one in the "Site" column.
Sorry, but I don't understand you exactly. What can I set on cookies? (A screenshot please.)
In the column "Site" in the "RSS Feeds" tab you should see the base name of the url for each tracker. I presume this value should be ncore.cc for your tracker. If it is, it should work to use ncore.cc in the cookie settings in the "Site URL" field.
You can PM me your config (yarss2.config) so I can test. Just obscure any sensitive values (replace some characters).
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.
and i managed to install the plugin from deluge preference
i have added my torrent feed, and make intervals 5 minutes
but untill now, no torrent has been added ! i can't see any torrent download !!!
PS: when i click add new subscription, nothing happens !!
Hi
I haven't tested with Deluge 1.3.1 so I'm not sure how that works. I recommend you install the latest Deluge version. You should use the latest YaRSS2 version which is YaRSS2-1.3.3-py2.6.egg. You should also delete the yarss2.conf file after upgrading to the latest YaRSS2 version.
When reporting issues, please include any relevant information such as OS (and version), python version (for Windows users this depends on which Deluge installer was used), Deluge version and plugin version.