search

Alanaktion / transmisson-remote-gui

Automatically exported from code.google.com/p/transmisson-remote-gui
GNU General Public License v2.0
1 stars 0 forks source link

Error message handling #206

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I use Transmission Remote GUI v1.3.2. 

After upgrading the daemon (linux ubuntu) to 1.92 (10363)
transmission-remote fails to display the correct error status. I.E. after a
temporary 'time out' (Tracker: tracker did not respond message) when the
daemon connects to the tracker the error message stays forever and the
status icon is always red. The error message is cleared only upon restart
of the daemon.

I believe this is related to http://trac.transmissionbt.com/ticket/3134

Original issue reported on code.google.com by eri...@gmail.com on 14 Apr 2010 at 7:49

GoogleCodeExporter commented 9 years ago 
I confirm. BTW TR.Net handles it seamlessly.

Original comment by leshekb on 24 Apr 2010 at 8:35

GoogleCodeExporter commented 9 years ago 
PS. dupe with #202.

Original comment by leshekb on 24 Apr 2010 at 8:36

GoogleCodeExporter commented 9 years ago 
This 'small' bug actually renders the otherwise wonderful utility useless. 

One never knows when there is a problem because the icon always stays red.

Original comment by eri...@gmail.com on 28 Apr 2010 at 8:03

GoogleCodeExporter commented 9 years ago 
Should be fixed by r250 and r252.

Original comment by j...@cp-lab.com on 30 Apr 2010 at 3:55

GoogleCodeExporter commented 9 years ago 
Compiled r256. Can not see the fix, TR.Net all green, TR-GUI most red.

Original comment by leshekb on 30 Apr 2010 at 4:44

GoogleCodeExporter commented 9 years ago 
What is displayed in the "Error" field on the torrent info page?
What the status of each tracker?

Original comment by j...@cp-lab.com on 30 Apr 2010 at 4:52

GoogleCodeExporter commented 9 years ago 
Checked carefully. It seems, TR.Net buggy itself - see attached picture. It 
does not
check status AT ALL!

Original comment by leshekb on 30 Apr 2010 at 5:06

Attachments:

GoogleCodeExporter commented 9 years ago 
Nice :)

Original comment by j...@cp-lab.com on 30 Apr 2010 at 5:15

GoogleCodeExporter commented 9 years ago

Original comment by j...@cp-lab.com on 30 Apr 2010 at 8:28

GoogleCodeExporter commented 9 years ago 
We need reopen this issue. If torrent was some time erroneous it will remain red
until transmission-daemon restarted. Tested and still confirmed, alas. Writes
"tracker not responding" in status.

Original comment by leshekb on 2 May 2010 at 7:37

GoogleCodeExporter commented 9 years ago 
Moreover, if I added torrent and tracker was somehow red I NEVER will start
downloading data later, until restarting daemon!

Original comment by leshekb on 2 May 2010 at 7:42

GoogleCodeExporter commented 9 years ago 
It make me guess that mabe it is daemon's bug...

Original comment by leshekb on 2 May 2010 at 7:43

GoogleCodeExporter commented 9 years ago 
What daemon version?
What tracker status on the Trackers page?

Original comment by j...@cp-lab.com on 2 May 2010 at 8:47

GoogleCodeExporter commented 9 years ago 
1.92. I said status is "not responding".

Original comment by leshekb on 2 May 2010 at 9:12

GoogleCodeExporter commented 9 years ago 
I have the same problem today and daemon restart solved it.
I will wait the problem to occur and I will investigate more...

Original comment by j...@cp-lab.com on 2 May 2010 at 9:21

GoogleCodeExporter commented 9 years ago 
Don't wait, just disconnect eth-cable for 2-3 min. :) Everything will red after
reconnecting.

Original comment by leshekb on 2 May 2010 at 9:38

GoogleCodeExporter commented 9 years ago 
Fixed in r285.

Original comment by j...@cp-lab.com on 2 May 2010 at 10:21

GoogleCodeExporter commented 9 years ago 
Sorry guys, but... now what? 
I can't compile the source for windows myself... 
Can I get some nightly builds somewhere?

Original comment by eri...@gmail.com on 4 May 2010 at 7:46