Transmission 1.42 Released (updated from 1.41)
Re: Transmission 1.42 Released (updated from 1.41)
Hi!
Version 1.42 works well, no more unresponsive hangs and having to force quit.
Thanks guys! You did a great job and quickly to fix the problems. Appreciate it. Transmission Rules!
Merry Christmas and Happy New Year.
Regards
KatanaS
Version 1.42 works well, no more unresponsive hangs and having to force quit.
Thanks guys! You did a great job and quickly to fix the problems. Appreciate it. Transmission Rules!
Merry Christmas and Happy New Year.
Regards
KatanaS
Re: Transmission 1.42 Released (updated from 1.41)
Hello folks,
first....Merry Christmas to all and Happy New Year
1.42 works perfect - Ubuntu 8.10 64bit
thank you
first....Merry Christmas to all and Happy New Year
1.42 works perfect - Ubuntu 8.10 64bit
thank you
Re: Transmission 1.42 Released (updated from 1.41)
Thumbs up for 1.42 on Mac 10.5.6! Great work you guys. You gave Mac torrents users a great Christmas
Merry X-Mas to all
Merry X-Mas to all
Re: Transmission 1.42 Released (updated from 1.41)
Thanks to the devs and testers! 1.42 is running beautifully on OS X 10.5.6.
Re: Transmission 1.42 Released (updated from 1.41)
Works great here! Awesome work guys!!!
20"iMac intel 2.66 Duo: 4GB RAM : OS 10.5.6
20"iMac intel 2.66 Duo: 4GB RAM : OS 10.5.6
Re: Transmission 1.42 Released (updated from 1.41)
Thanks for 1.42...it complied fine against curl-7.19.2 on my Centos box and has been happly uploading/downloading for the last hour. Bandwidth limits are looking good and the distribution between torrents seem to be working also.
I also am using the black lists from Bluetrack in this release which should keep the nasties away from me....
Thank you guys for all the hard work you put into this relase. I had fun testing the beta software this time please keep the beta code coming.....
I also am using the black lists from Bluetrack in this release which should keep the nasties away from me....
Thank you guys for all the hard work you put into this relase. I had fun testing the beta software this time please keep the beta code coming.....
Re: Transmission 1.42 Released; bug?
FYI: Possible bug in Transmission 1.42 (7494) when torrent size > free space.
Transmission 1.42 (7494) has quit the first 10 times I launched it. Only once did the Mac catch it with "Transmission quit unexpectedly,,, close report reopen. I have Mac dual G5, OS 10.4.11.
Looking at Apples "Console", under "system.log" I see...
Dec 25 20:42:40 CCG5 KernelEventAgent[35]: tid 00000000 received VQ_LOWDISK event (4)
Dec 25 20:42:40 CCG5 KernelEventAgent[35]: tid 00000000 type 'hfs', mounted on '/Volumes/LaCie_2ndTB', from '/dev/disk3s6', low disk
This *may* be correct, but I was retrieving only 500kB out of 500MB from torrent. If disk allocation was for full torrent contents, the disk *would* have been full.
After pulling Transmission 1.40 (7084) out of trash, I got the nice yellow error triangle saying disk is full, but Transmission did not quit.
I'll try 1.42 again now that I've freed up some space.
Thanks for the great software!
takeTwo
Transmission 1.42 (7494) has quit the first 10 times I launched it. Only once did the Mac catch it with "Transmission quit unexpectedly,,, close report reopen. I have Mac dual G5, OS 10.4.11.
Looking at Apples "Console", under "system.log" I see...
Dec 25 20:42:40 CCG5 KernelEventAgent[35]: tid 00000000 received VQ_LOWDISK event (4)
Dec 25 20:42:40 CCG5 KernelEventAgent[35]: tid 00000000 type 'hfs', mounted on '/Volumes/LaCie_2ndTB', from '/dev/disk3s6', low disk
This *may* be correct, but I was retrieving only 500kB out of 500MB from torrent. If disk allocation was for full torrent contents, the disk *would* have been full.
After pulling Transmission 1.40 (7084) out of trash, I got the nice yellow error triangle saying disk is full, but Transmission did not quit.
I'll try 1.42 again now that I've freed up some space.
Thanks for the great software!
takeTwo
Re: Transmission 1.42 Released (updated from 1.41)
Why is the display of the upload speed always rounded to x.0 KB? Don't know if it's the same for download speed since I am not downloading at the moment.
If I remember correctly this wasn't always the case
If I remember correctly this wasn't always the case
-
- Posts: 2
- Joined: Sun Dec 28, 2008 3:03 am
Re: Transmission 1.42 Released (updated from 1.41)
I've just updated (again) to Transmission 1.42 and yet again I've been disappointed. The last time I tried this version the downloads were less than 1.34. This time I thought I'd give it a go again and absolutely nothing is happening. I running an Intel aluminum iMac with the latest version of Tiger. I'm using a public download and I've checked everything and deleted the Transmission preferences. I likewise had problems with Transmission 1.40 with error message but at least I could get that version to work. I guess it's time to downgrade again (sigh). Despite all that I wish everyone in the Transmission team a happy new year and a productive '09.
Re: Transmission 1.42 Released (updated from 1.41)
With the released version I ran into several problems yesterday:
I tried pausing a torrent and starting it again after a long time, no change.
Finally I stopped the daemon (this is when I had problems stopping it, it didn't respond until the 3rd or 4th attempt using the inti.d script) and started it again. The result is that all torrents were seen fine on all trackers, only weird thing was that one torrent was connected twice (this is something I've seen before, with older transmission versions, it happens very seldom but one daemon connects twice to a tracker, as in two sessions, and it stays that way).
The main problem is hard to duplicate, I would need to watch from the tracker side all the time to see the disconnection (and some trackers are not reliable enough for this, they show bogus disconnections, but yesterday it was 2 different trackers and for a long time, so I'm sure the daemon was not seeding).
There was strange dates in the tracker info (this is when the daemon was not really seeding):
Notice the "Next announce" and "Next scrape" dates? to any person with Unix experience it means a big zero translated to a date.
Did that came from the tracker or the daemon? and, is that the cause of the problem?
- Daemon stops seeding idle torrents after some time;
- Daemon connects more than once simultaneously to tracker;
- Daemon is hard to stop.
I tried pausing a torrent and starting it again after a long time, no change.
Finally I stopped the daemon (this is when I had problems stopping it, it didn't respond until the 3rd or 4th attempt using the inti.d script) and started it again. The result is that all torrents were seen fine on all trackers, only weird thing was that one torrent was connected twice (this is something I've seen before, with older transmission versions, it happens very seldom but one daemon connects twice to a tracker, as in two sessions, and it stays that way).
The main problem is hard to duplicate, I would need to watch from the tracker side all the time to see the disconnection (and some trackers are not reliable enough for this, they show bogus disconnections, but yesterday it was 2 different trackers and for a long time, so I'm sure the daemon was not seeding).
There was strange dates in the tracker info (this is when the daemon was not really seeding):
Code: Select all
$ transmission-remote -n aaa:bbb -t 34 -i
NAME
Id: 34
Name: Taaa
Hash: 0xxx
TRANSFER
State: Idle
Percent Done: 100%
ETA: Unknown
Download Speed: 0.0 KB/s
Upload Speed: 0.0 KB/s
Have: 1.4 GB (1.4 GB verified)
Total size: 1.4 GB (1.4 GB wanted)
Downloaded: 1.4 GB
Uploaded: 1.5 MB
Ratio: 0.00
Corrupt DL: None
Peers: connected to 0, uploading to 0, downloading from 0
HISTORY
Date added: Sat Jan 3 18:33:36 2009
Date finished: Sat Jan 3 21:41:45 2009
Date started: Sat Jan 3 18:33:36 2009
Latest activity: Sun Jan 4 10:39:08 2009
TRACKER
Latest announce: Sun Jan 4 10:19:58 2009
Announce URL: http://xxx
Announce response: OK (200)
Next announce: Wed Dec 31 18:00:01 1969
Latest scrape: Sun Jan 4 10:27:42 2009
Scrape response: OK (200)
Next scrape: Wed Dec 31 18:00:01 1969
Tracker knows of 5 seeders and 1 leechers
Tracker has seen 4 clients complete this torrent
ORIGINS
Date created: Sat Jan 3 04:52:37 2009
Public torrent: No
Comment: seed for speed
Creator: xxx
Piece Count: 705
Piece Size: 2097152
Did that came from the tracker or the daemon? and, is that the cause of the problem?
Re: Transmission 1.42 Released (updated from 1.41)
Follow up on my last message: it did it again, its definitely a bug on 1.42, it stops seeding after it mis-calculates the next scrape time. And the daemon is hard to stop, 3 failed tries, on the 4th it succeeds.
I'm opening a bug report on trac.
I'm opening a bug report on trac.
Re: Transmission 1.42 Released (updated from 1.41)
Transmission needs a serious overhaul. It's been some time since the developers produced a stable release.
regards
Re: Transmission 1.42 Released (updated from 1.41)
Transmission 1.42 (7494) is working just fine for me. It's working well enough that I'm hesitant to try the 1.5 beta.
Re: download speed and connections: I've always wondered whether Trans was connecting to all possible peers, so I tried the uTorrent beta. Based on limited use of the uTorrent beta, IMO Trans 1.42 did just as well in terms of both connections and speed -- and I liked Transmission's GUI a whole lot better.
I'm running 1.42 on a 2.5 GHz Intel Core 2 Duo MBP with 4GB of RAM, under OS X v. 10.5.6, with a wireless connection.
Kudos to the developers!
Re: download speed and connections: I've always wondered whether Trans was connecting to all possible peers, so I tried the uTorrent beta. Based on limited use of the uTorrent beta, IMO Trans 1.42 did just as well in terms of both connections and speed -- and I liked Transmission's GUI a whole lot better.
I'm running 1.42 on a 2.5 GHz Intel Core 2 Duo MBP with 4GB of RAM, under OS X v. 10.5.6, with a wireless connection.
Kudos to the developers!