Transmission

Posted: **Sat Aug 06, 2011 2:31 am**

Hi all,

I use transmission-remote on cygwin frequently to control my transmission-deamon running on headless linux server. I downloaded nightly sources from transmissionbt.com and compile it on cygwin. With last a few releases after 2.33, I've noticed some wrong status info and garbage like:

Code: Select all

transmission-remote 2.33+ (12629)

ID     Done       Have  ETA           Up    Down  Ratio  Status       Name
   1   100%   5.98 GiB  Done         0.0     0.0    524  ▒U$a         <<intentional blank>>
   2   100%   4.42 GiB  Done         0.0     0.0   0.00  ▒U$a         <<intentional blank>>
   3   100%   5.43 GiB  Done         0.0     0.0   0.07  ▒U$a        <<intentional blank>> 
   4   100%   8.15 GiB  Done         0.0     0.0   0.12  ▒U$a         <<intentional blank>>
   5   100%   4.36 GiB  Done         0.0     0.0   0.04  ▒U$a        <<intentional blank>>

Code: Select all

transmission-daemon
VERSION
  Daemon version: 2.32 (12526)
  RPC version: 13
  RPC minimum version: 1

I appreciate any hint and advises. Thank you

Posted: **Sat Aug 06, 2011 4:04 am**

transmission-remote 2.33+ (12629)
transmission-daemon 2.32 (12526)

because of new feature "Torrent Queuing" introduced recently in the nightly builds https://trac.transmissionbt.com/changeset/12607 the torrent status fields have changed, among a lot of other things. I believe that's why you're seeing some garbage there .. solution would be to match daemon and remote build numbers much more closely than you have now.

i'm seeing related RPC issues with a third-party remote client at the moment.

Transmission

Garbase in transmission-remote screen

Garbase in transmission-remote screen

Re: Garbase in transmission-remote screen