Basically I mean that I'm half blind but also that I expected a 'Register' link on the login form, as the standard usually as.

Anyway, thanks for pointing me towards the registration link. The bug report is http://dev.deluge-torrent.org/ticket/1481

I don't have a login for the Deluge bug tracker, and it does not allow registrations, that's why I'm reporting bugs through the forums.

I am unable to add a torrent to deluge through the Web UI, I have to use the command line or the GTK client. I have apache proxying setup so that Deluge works in /deluge/ path on the same port that Apache uses. When I try to add a torrent from Firefox (3.6 or 4), upload file does not work, only gett...

I can no longer reproduce this, however I can't find what has changed. I'm running now the combination that was failing before and it works fine.

stacktrace from the segmentation fault

Using Deluge 1.3.1 with pyopenssl 0.11 results with Segmentation Faults no matter what I do. Reverting to pyopenssl 0.10 fixes the problem. Recompiling Deluge with the new pyopenssl installed does not help.

Using deluge 1.3.0 and rb_libtorrent 0.15.4 this bug still manifests, I'm checking deluge 1.3.1 (which is supposed to fix the web-interface 100% CPU usage bug) right now and things seem to be much better.

On deluge 1.3.0 and rb_libtorrent 0.15.1 today I hit 100% cpu usage during download, although this did not happen before. I'll check rb_libtorrent 0.15.4.

It seems that the problem manifests on on AMD and Intel Atom CPUs, anyone experiencing it on a Intel Core machine?