Transmission

With any 2.30/2.31 build I tried, svn or tarball, initially upon start Transmission would seed all six torrents to the requesting leecher, but after 30-60 minutes it would stop seeding and would not resume seeding despite any prodding I knew to use (pause/start, unload/reload, ritual human sacrific...

Update: I've been working with some support staff at a tracker I use, and they can confirm the behaviour, and have postulated that it could be a misbehaving superseeding implementation. In any case, I have downgraded from 2.31 to 2.22 and the problem has gone away, so I'm just putting it out there t...

I can confirm I have been having this problem, even for torrents I am uploading, for about 2 weeks as well. Restarting the client seems to clear the issue for about 20-30 minutes then I go back to having several leachers, no seeders other than me, and I am not connected to any peers. I have been wor...

I had a similar problem to this as well. The issue turned out to be that my downloads directory was still pointing to a drive that wasn't connected. I could tell, because every time I tried to start a new torrent, the old drive mount point would appear in /Volumes and I'd delete it again. Simply re-...