Custom Query (2449 matches)

I get segfaults running deluge, like twice every day (host runs through several days) From dmesg I can read messages like this: deluge[26295]: segfault at 7f80f9ffcf78 ip 00007f810e95a4dc sp 00007f80f9ffcf80 error 6 in libtorrent-rasterbar.so.6.0.0[7f810e7f0000+28b000]

Maybe I can reprod or get a stacktrace with symbols but I don't think I have the time for building the program myself. I just let it run, I don't do anything before it crashes. I also don't use the webclient, just deluge-gtk.

I hope this can help improving this nice software.

When a seeding torrent data is moved on the file-system from outside deluge, deluge starts thinking it's a new torrent and starts downloading it again(at least within server restarts). The correct behaviour would be to error the torrent giving it a meaningful status message like "Downloaded torrent data not found" or something like this, and if the user actually wants to re-download the torrent, have him resume it.

Would there be interest into switching from gettext to ​Babel?

• All built in python
• Glade string extraction support(extension)
• Javascript support (for webui).
• Catalog Extract/Complile/Merge/Update plus translated statistics for each or all catalogs, which can be as simple as python setup.py extract_messages, etc...
• Available at least on debian/ubuntu(I don't run any other distros) as a package.

If there's enough interest, I'd be happy to create the necessary code changes to be reviewed by a developer.