Deluge Forum

Ever since I upgraded to v0.5.8.3 I have been noticing intermittent (but none the less frequent) hangs when launching Deluge (maybe 3 out of every 5 launches are affected). The deluge window opens, but none of the window contents (panes, toolbar etc,) are visible because the deluge window is frozen.

At first I thought it was the Blocklist plugin causing problems, but even after disabling the Blocklist plugin the problem continued.

After trying various different things, I seemed to track the problem down to Deluge's update notifcation.

If I turn off the setting that says: "Be alerted about new releases" then Deluge starts fine. However if I activate this setting then Deluge starts hanging when it's launched. It doesn't happen straight away, it's maybe two or three launches later that the problems start.

I have tried deleted the entire deluge folder in ~/.config but it made no difference. So then I tried launching Deluge from the command line. It took 5 launch attempts before the problem reoccurred and the error message in the console was:

Network error while trying to check for a newer version of Deluge

Has anyone experienced a similar problem?

Incidentally, (I don't know if it's related) but I've been having loads of problems with this forum timing out when trying to access pages.

The past week they were updating to a new server, this could be related to that...

loki wrote:The past week they were updating to a new server, this could be related to that...

yes, it was because we were switching servers and things went to hell. this should be fixed from here on out....sorry

this should be fixed from here on out....sorry

No probs.

Just thought I'd mention it as I wasn't exactly sure what the cause was.

Thank you for the clarification (and for a great program).

P.S. (cont. from my post above)

Perhaps an adjustment could be made so that at least the UI displays in full even if the notification server is not reachable (possibly by performing the update check a little later in the launch process). At the moment you just get a blank unresponsive window at program launch with no indication as to why. At least if the UI was up and running then status bar message (or dialog) could relay the unavailability of the update notification server to the user.

Just a suggestion, but as I'm not a programmer I don't know how feasible this would be.