Transmission

Since they are private trackers, are you sure they are allowing 1.83 yet. Typically, they do not allow new clients right away. Also, are you sure the problem isn't on the tracker's end? I'm looking at the network traffic to the trackers with tcpdump right now... and there is none. 1.83 does not eve...

livings124 wrote:How many trackers have you tried with? Are you sure this isn't on the tracker's end.

Two private trackers I currently have torrents on. 1.83 can't get anything from the trackers. 1.82 right away gets peers and peer counts from the very same trackers.

I just built and tried 1.83, and it fails to retrieve any peers or peer counts from trackers. 1.82 seems to work fine in this respect.

(GTK, OpenBSD/sparc64.)

Just as a follow-up, 1.74 is fine for me on OpenBSD/sparc64 where Beta 1 failed. To respond to some of the questions asked over in the Beta 1 thread: The default stack size for a thread is 512kB. Running Transmission under valgrind is not an option, because there is no valgrind port for this platfor...

Jordan wrote:Still, it might help Juliusz (the DHT author) a bit. I've mailed him a heads-up and pointed him to this thread.

dht_periodic() might be a red herring. I just tried 1.74b1 with the dht from 1.73, and I get the same error.

Built it on OpenBSD/sparc64, which is a good platform for finding bugs, and the GTK client dies a few seconds after starting up with a stack smash in dht_periodic(). 1.73 was fine. Any more information you can give on this? Not really. The backtrace isn't very enlightening. (gdb) bt #0 __stack_smas...

Built it on OpenBSD/sparc64, which is a good platform for finding bugs, and the GTK client dies a few seconds after starting up with a stack smash in dht_periodic(). 1.73 was fine.

Out of idle curiosity I looked into the message log and noticed this: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) Port Forwarding (UPnP) Found Internet Gateway Device "http://172.16.0.99/" Port Forwarding (UPnP) Local ...

transmission-remote.1 fails to mention the new --session option.

The settings in the Preferences->Bandwidth tab of the GTK client interact in unexpected ways. When the scheduled limits are active (1) if I change the general limits, the settings immediately take hold and override the scheduled limits. If I then change the scheduled limits, they take hold again; bu...

If the compiler is detected as gcc, the configure script adds flags to CFLAGS that are only supported by gcc 4.x and not by gcc 3.x: -Wextra, -Wdeclaration-after-statement, -Winit-self. I think I've got this fixed, but don't have an old build of gcc handy to test on... you may want to do an svn tru...

At least the GTK client doesn't listen on IPv6 for the RPC interface, only for peer connections.

If the compiler is detected as gcc, the configure script adds flags to CFLAGS that are only supported by gcc 4.x and not by gcc 3.x: -Wextra, -Wdeclaration-after-statement, -Winit-self.

(gcc 2.x may trip over some additional flags, I haven't tried.)

At least the GTK client doesn't listen on IPv6 for the RPC interface, only for peer connections.