Transmission

All tickets closed by this release

All Platforms

• Fix rare crash when some peers disconnected unexpectedly
• Fix bug which didn't parse scheduled speed limit dates correctly
• Fix bug that broke magnet links whose names contained slashes
• Fix crash when updating the blocklist when the disk is full
• Fix slow file preallocation on Unix systems not using ext3/ext4
• Fix regression which broke the "bind-address-ipv4" configuration setting
• For better security, Web client connections are disabled by default
• Update to miniupnpc-1.4
• Transmission builds out-of-the-box with Curl 7.15.5. (Hello CentOS!)

GTK+

• Use the size for the system tray icon

Qt

• Fix bug that crashed when removing more than one torrent at once
• Fix bug when parsing the remote password from the command line
• Add support for the "incomplete directory" in the preferences dialog
• Don't show "time remaining" for paused torrents

Daemon

• Fix bug parsing RPC requests when setting which files to not download
• Fix possible crash when using inotify for the daemon's watchdir
• Fix bugs in the configure script
• Fix bug updating the blocklist over RPC

Web Client

• Fix bug that broke the "reverse sort order" menu checkbox

http://www.transmissionbt.com/download.php

x190: That functionality's been there for a while.

Thanks for the update. Still the best torrent client around.

Problem shown in the log starting the daemon:

transmission-daemon: Unable to watch ""/export/home/xyz/.transmission/torrentwatch/"": No such file or directory (watch.c:90)

The directory does exist, it belongs to the user running the daemon, and has the correct permissions (in fact it hasn't been changed at all and it has been in use with all the previous versions that had a watch dir).

Not a big problem but its a bug.

Also shown in the log:

transmission-daemon: blocklist skipped invalid address at line 243778 (blocklist.c:286)

The line mentioned has an extra space between a range of IP addresses. Since I don't make the blocklists, in this case moBlock makes them joining a number of block lists, does the line parsing has to be so strict?

BTW the list doesn't seem to be skipped, the created .bin is there, my guess is that parsing just stopped at that line and skipped everything else.

Problem: transmission-remote on ARM based NAS stops responding after less than 2 days of running.

By "stops responding" I mean it doesn't respond on the Web client, and to transmission-remote, and to any peers and trackers so it just runs doing nothing. An strace shows: The errno 38 is probably bogus, it does the same with a normal running daemon.

Thanks for the update!! I'm new to tranmission as of 1.92 running on my DNS-323 and LOVE it along with tranmission-remote-gui. Best software ever!

Well hate to be the bringer of bad news but still crash city here.

Happens when left overnight. We roll into offpeak downloads at 2am so the timer is set to open the torrents up to full speed at this time.

For some reason though the system just beachballs and then becomes un responsive. Having to use the power button to restart the whole system and no crash report.

note that this issue isnt happening when swapping back to onpeak and limiting the downloads again.

Few other minor details . System running all updated patches (10.6.3) no other app does this only transmission.

hmm seems like someone did't correctly publish 1.93 in my devices optware feed.. I keep getting the following error.

Collected errors:
ipkg_download: ERROR: Command failed with return value 8: `wget --passive-ftp -q -P /opt/ipkg-2okAD4 http://ipkg.nslu2-linux.org/feeds/optwa ... -1_arm.ipk'


Not sure who should be notified about that .. I noticed the file is in the /cross/unstable folder on that server.

lazybones wrote:hmm seems like someone did't correctly publish 1.93 in my devices optware feed.. I keep getting the following error.

Collected errors:
ipkg_download: ERROR: Command failed with return value 8: `wget --passive-ftp -q -P /opt/ipkg-2okAD4 http://ipkg.nslu2-linux.org/feeds/optwa ... -1_arm.ipk'


Not sure who should be notified about that .. I noticed the file is in the /cross/unstable folder on that server.

You'd need to contact your optware packager about that. We don't have any control over that... I don't even know who does that packaging.

I am not sure who packages it ether. I know it isn't the transmission devs.. Just posted it here in case anyone knew.

boy these last few versions of transmission have been miserable, i switched back to transmission in hopes it would be better, but i get nonstop crashes on 3 computers all running 10.6.3 with 1.93 and 1.92, then if i reopen the torrents get stuck checking for data, which never resolves, so basically i have 100GB of unfinished torrents that i'll have to restart because transmission has decided to go ape shit. utorrent here i come.

katiepea: Can you post the crash logs?