gnome-btdownload can have a ridiculous amount of error message windows.

[lexual]

I am running breezy.

I had 4 gnome-btdownload windows downloading 4 torrents. I returned to my
computer later on in the day to find the taskbar had a lot more gnome-btdownload
windows, the original 4 windows plus a heap of error message windows.

TASKBAR: gnome-btdownload (39)

Each window has the title "untitled window", with the text Problem connecting to
tracker, timeout exceeded.

Now even if these are really bad torrents, this situation should be handled a
lot more elegantly.

Currently I have to >30 windows when I return to my computer.

[lexual (lexhider)]

line should read that I have to CLOSE >30 windows when I return to my computer.

[lexual (lexhider)]

I now realize this more than just an annoyance.
Returned to my computer to find >300 error dialog windows and it tied up my
memory/cpu for a while closing all those windows.

[Richard Quirk (quirky)]

This is my attempt at an easy quick-fix:
Open the file /usr/bin/gnome-btdownload in a text editor.
go to line 734.
Comment the line out or remove it:
#GtkHigErrorDialog('<b>' + mo.group(1) + '</b>', mo.group(2))
Now go down a couple of lines to line 736, comment out the line and add the line 'pass':
pass
#GtkHigErrorDialog(str(text))

Any errors are logged in the Events tab already, so the information is not lost. This is a quick hack to stop the irritation - anything is better than a pop-up dialog. A perhaps better method would be to show the last error in red on the Download tab together with the time-stamp.

[Richard Quirk (quirky)]

I've just realised that (in Breezy at least) there is a check-box "Display Error Dialogs" on the Events tab! Unchecking this stops the annoying dialogs (talk about a sledgehammer to crack a nut with my hacks above).

Perhaps by default this checkbox should be set to not show the dialogs?

[Matt Zimmerman (mdz)]

This bug has been forwarded to the author via the upstream bug tracker

[Andrew Jorgensen (ajorg)]

The upstream bug report says this has been fixed in 0.25 (released in July).

Not sure why launchpad doesn't see that.

[Andrea Veri (av)]

Seems to be fixed in version 0.0.25. Anyway 0.0.28 has been released and packaged. If you can still reproduce this, re-open the bug.

Thanks for your work.