Transmission 1.50 beta 3

Discussion of Transmission that doesn't fit in the other categories
Jordan
Transmission Developer
Posts: 2311
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Transmission 1.50 beta 3

Post by Jordan »

Transmission 1.50 Beta 3 is now available for download.

About 1.50: 1.50 doesn't have many visual changes, but has lots of improvements under the hood, including IPv6 support, better management of peers, trackers, and local files, and lots of bug fixes.

About 1.50 beta 3: this beta has three high-priority peer connectivity fixes: one affecting mac users, one affecting encrypted peer traffic, and one affecting swarms with low peer counts. Also, the "add torrent by URL" feature has been reintroduced into the Web UI.
el1216
Posts: 1
Joined: Fri Jan 23, 2009 11:59 am

Re: Transmission 1.50 beta 3

Post by el1216 »

Transmission 1.50 beta 3 succesfully ported to Dreambox DM800 , MIPS architecture cpu model Brcm7401
Working stable. Thank you for your work !
naddy
Posts: 19
Joined: Thu Dec 04, 2008 7:09 pm

Re: Transmission 1.50 beta 3

Post by naddy »

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.)
naddy
Posts: 19
Joined: Thu Dec 04, 2008 7:09 pm

Re: Transmission 1.50 beta 3

Post by naddy »

At least the GTK client doesn't listen on IPv6 for the RPC interface, only for peer connections.
Jordan
Transmission Developer
Posts: 2311
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Re: Transmission 1.50 beta 3

Post by Jordan »

naddy wrote: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.)
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 trunk checkout and confirm that the problem is solved there.
naddy
Posts: 19
Joined: Thu Dec 04, 2008 7:09 pm

Re: Transmission 1.50 beta 3

Post by naddy »

Jordan wrote:
naddy wrote: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 trunk checkout and confirm that the problem is solved there.
Yes, this is fixed. Thanks.
KingJulian
Posts: 30
Joined: Sun Dec 21, 2008 5:32 pm

Re: Transmission 1.50 beta 3

Post by KingJulian »

Seems fine on my mac for now, except for quitting unexpectedly ones:

Code: Select all

Process:         Transmission [97531]
Path:            /Applications/Transmission.app/Contents/MacOS/Transmission
Identifier:      org.m0k.transmission
Version:         1.50b3 (7776)
Code Type:       X86 (Native)
Parent Process:  launchd [175]

Date/Time:       2009-01-24 02:33:21.341 +0300
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  1

Thread 1 Crashed:
0   libSystem.B.dylib             	0x904bafd6 usleep$NOCANCEL$UNIX2003 + 0
1   libSystem.B.dylib             	0x904d2685 abort + 85
2   org.m0k.transmission          	0x000929f4 0x1000 + 596468
3   org.m0k.transmission          	0x00070597 0x1000 + 456087
4   org.m0k.transmission          	0x00089657 0x1000 + 558679
5   org.m0k.transmission          	0x00089a73 0x1000 + 559731
6   org.m0k.transmission          	0x0006afd4 0x1000 + 434132
7   libSystem.B.dylib             	0x90417095 _pthread_start + 321
8   libSystem.B.dylib             	0x90416f52 thread_start + 34
DaveF1
Posts: 11
Joined: Mon Dec 31, 2007 12:27 pm

Re: Transmission 1.50 beta 3

Post by DaveF1 »

1.50 beta 3 still doesn't appear to obey upload limits (either that or its misreporting the speed). Running headless on NSLU2 using Transmission Remote, Transmission Remote GUI or inbuilt clutch to monitor. I still don't know whether slow d/l speeds are due to me or ISP throttling - must try another client to compare... thanks for all the hard work that's obviously going into this.
Jordan
Transmission Developer
Posts: 2311
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Re: Transmission 1.50 beta 3

Post by Jordan »

KingJulian wrote:Seems fine on my mac for now, except for quitting unexpectedly once:

Code: Select all

Thread 1 Crashed:
0   libSystem.B.dylib             	0x904bafd6 usleep$NOCANCEL$UNIX2003 + 0
1   libSystem.B.dylib             	0x904d2685 abort + 85
2   org.m0k.transmission          	0x000929f4 0x1000 + 596468
3   org.m0k.transmission          	0x00070597 0x1000 + 456087
4   org.m0k.transmission          	0x00089657 0x1000 + 558679
5   org.m0k.transmission          	0x00089a73 0x1000 + 559731
6   org.m0k.transmission          	0x0006afd4 0x1000 + 434132
7   libSystem.B.dylib             	0x90417095 _pthread_start + 321
8   libSystem.B.dylib             	0x90416f52 thread_start + 34
This looks like there ought to be an assertion failure to go with it. Could you check your console log (for more details on how to do this, see the "How To Report a Bug" post at the top of this forum) and, if there's an assertion failure, post it here?
naddy
Posts: 19
Joined: Thu Dec 04, 2008 7:09 pm

Re: Transmission 1.50 beta 3

Post by naddy »

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; but

(2) if I change the scheduled limits, [Close] the preferences window, open the preferences again, the general limits have taken on the values of the scheduled limits.

In practical terms, this means that during the time period where the scheduled limits are active I cannot set the general limits to values different from the scheduled limits.
sin4me
Posts: 6
Joined: Mon Dec 08, 2008 3:03 pm

Re: Transmission 1.50 beta 3

Post by sin4me »

Upgraded from v 1.22 to 1.50b3 since I was having problems seeding with a trackers. Still not able to seed to the trackers I was initially having issues with but, this new version is way faster when establishing connections to peers on other (known working) trackers.

OT: Regarding the trackers I was unable to seed to, I took a leap and installed the latest uTorrent - problem still exists with that client as well, so I doubt it has anything to do with the older version of Transmission I was previously using. Furthermore, Transmission is much more enjoyable to use. Thanks for the great work!
Nemo
Posts: 17
Joined: Sun Dec 30, 2007 8:49 pm
Location: the Netherlands

Re: Transmission 1.50 beta 3

Post by Nemo »

I've been working on the Dutch translation for the GTK-version of Transmission 1.5 beta using Launchpad. (which now is 100% translated again)

A fellow translator who reviewed my translations, suggested that translations for column-labels should use 'context'? So instead of using _("Download") using something like C_("column-label|Download")?

I myself don't know anything about coding, so I've got no idea, but maybe the devs have a opinion about this?
b0baz
Posts: 9
Joined: Sun Oct 26, 2008 4:25 pm

Re: Transmission 1.50 beta 3

Post by b0baz »

Hey guys,

absolutely OK on my Ubuntu 8.04 64bit.
No problem detected. (Transmission is running 24/7).
Peer connection and speed are very good and stable. Other things OK too.

No problemo, thank you. 8-)
fonam
Posts: 50
Joined: Fri Nov 16, 2007 12:47 pm

Re: Transmission 1.50 beta 3

Post by fonam »

I still get a lot of "erno 65 - no route to host" messages just after start-up of Transmission. During operation it appears once in a while. Up-/download speeds look oke, but still seems to be some glitch in the connectivity to peers. But overall it's an improvement compared to 1.50 beta 2, where those messages were a lot worse. Ticket 1717
overlook
Posts: 104
Joined: Wed Feb 08, 2006 5:15 pm

Re: Transmission 1.50 beta 3

Post by overlook »

fonam wrote:I still get a lot of "erno 65 - no route to host" messages just after start-up of Transmission. During operation it appears once in a while. Up-/download speeds look oke, but still seems to be some glitch in the connectivity to peers. But overall it's an improvement compared to 1.50 beta 2, where those messages were a lot worse. Ticket 1717
I've same problem...

Code: Select all

2009-01-26 01:56:58 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 49 to 2001::4137:9e50:e4:1d65:b876:557, port 59162 (errno 65 - No route to host)
2009-01-26 01:56:58 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 49 to 2001::4137:9e50:387a:13d9:b94b:2317, port 23613 (errno 65 - No route to host)
2009-01-26 01:57:00 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 56 to 2001::cf2e:3096:0:fa58:b0e1:49c2, port 23796 (errno 65 - No route to host)
2009-01-26 01:57:00 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 56 to 2001::cf2e:3096:4bb:498:b0e4:bbe9, port 46717 (errno 65 - No route to host)
2009-01-26 01:57:02 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 75 to 2001::cf2e:3096:c60:800:a8f8:95cb, port 36752 (errno 65 - No route to host)
2009-01-26 01:57:02 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 75 to 2001::cf2e:3096:1079:10e0:b0ed:13aa, port 57082 (errno 65 - No route to host)
2009-01-26 01:57:02 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 75 to 2001::cf2e:3096:146e:2738:a1db:751f, port 44352 (errno 65 - No route to host)
2009-01-26 01:57:02 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 75 to 2001::cf2e:3096:18c9:d3b:b0f0:174a, port 17043 (errno 65 - No route to host)
2009-01-26 01:57:02 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 75 to 2001::cf2e:3096:20da:10fd:b0eb:c176, port 8432 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::cf2e:3096:2435:9dd4:a26f:c4cb, port 59287 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::cf2e:3096:3076:d54a:c184:d8de, port 32837 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::cf2e:3096:387d:1165:b0f4:a594, port 5187 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::cf2e:3096:3885:9154:b0ea:5689, port 59123 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::cf2e:3096:8000:fbfe:b0ed:81a7, port 56070 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::d5c7:a2d6:0:eed3:b0f2:ecd2, port 11577 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::d5c7:a2d6:cb:b969:b0ee:a74f, port 5942 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::d5c7:a2d6:cf:3021:b0fc:44c3, port 3957 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::d5c7:a2d6:c41:2ca0:3f57:ff65, port 55669 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::d5c7:a2d6:1c00:25be:b0f2:fb5b, port 17057 (errno 65 - No route to host)
2009-01-26 01:57:04 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 76 to 2001::d5c7:a2d6:2027:25cf:3f57:fedd, port 62780 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::4137:9e50:4a5:28dd:a39e:5bd3, port 52049 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::cf2e:3096:243d:65e:a8f1:6a42, port 59012 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::cf2e:3096:2c22:c2b:3f57:fdfd, port 59418 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::cf2e:3096:8000:fbfb:a8e6:94ed, port 11034 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::d5c7:a2d6:2053:32e4:a8fe:3087, port 31787 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::d5c7:a2d6:245d:fbff:b0f1:1dad, port 56712 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::d5c7:a2d6:24af:383c:b0ef:4c38, port 53801 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::d5c7:a2d6:24ea:2b1f:a8f3:d91d, port 20271 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::d5c7:a2d6:28c5:3f46:b0e1:f473, port 18595 (errno 65 - No route to host)
2009-01-26 01:57:06 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 83 to 2001::d5c7:a2d6:2c73:26c4:b0ff:7a5f, port 55540 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:2ca5:1514:a8f2:77ae, port 53577 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:2cd1:2920:b1f0:7953, port 52879 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:2ced:41f:b0f4:fda4, port 60216 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:302e:1e19:b1f0:a621, port 5961 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:30f0:c549:c1cf:8568, port 40694 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:3823:45:b0f5:183e, port 65263 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:3831:92b5:b0f7:da39, port 59645 (errno 65 - No route to host)
2009-01-26 01:57:08 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 84 to 2001::d5c7:a2d6:3844:d644:b0eb:8a3d, port 43230 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2001::d5c7:a2d6:3a:180e:b0e7:8c52, port 55738 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2001::d5c7:a2d6:3c99:13dc:c12c:452b, port 39985 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2001::d5c7:a2d6:3ca7:2972:3f57:fefd, port 25795 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2001::d5c7:a2d6:3cb8:32f:b0ea:50c, port 39095 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2001::d5c7:a2d6:8000:f140:b0e6:a2c8, port 41796 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2002:3e5e:381d::3e5e:381d, port 11113 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2002:4f0a:cff3::4f0a:cff3, port 9515 (errno 65 - No route to host)
2009-01-26 01:57:10 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 87 to 2002:4f0d:44a4::4f0d:44a4, port 60476 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to 2002:4f1b:b1f6::4f1b:b1f6, port 13911 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to 2002:4f1e:284c::4f1e:284c, port 46237 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to 2002:4f33:98d0::4f33:98d0, port 50451 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to 2002:5074:b5fd::5074:b5fd, port 14619 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to fe80::ffff:ffff:fffe, port 53313 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to fe80::201:4aff:fe5e:82c6, port 62286 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to fe80::20a:e4ff:fea1:d18a, port 14563 (errno 65 - No route to host)
2009-01-26 01:57:12 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 108 to fe80::20e:e8ff:fef8:25b, port 9351 (errno 65 - No route to host)
2009-01-26 01:57:14 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 47 to fe80::215:60ff:fec6:4750, port 13280 (errno 65 - No route to host)
2009-01-26 01:57:14 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 47 to fe80::218:feff:fe6f:1c68, port 57626 (errno 65 - No route to host)
2009-01-26 01:57:56 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 128 to 2001::cf2e:3096:201a:4b1:b0f5:8a06, port 47040 (errno 65 - No route to host)
2009-01-26 01:57:56 +0100 net.c:522 [Error] Transmission: Couldn't connect socket 128 to 2001::d5c7:a2d6:836:36e6:b0e0:e442, port 3758 (errno 65 - No route to host)
Locked