Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#4277 closed Bug (fixed)

Checkmarks for leechers

Reported by: wingnutsc Owned by: jordan
Priority: Normal Milestone: 2.32
Component: libtransmission Version: 2.31
Severity: Normal Keywords:
Cc: shawn.bissell@…


As per this topic:

Here is an example of the problem involving a torrent that has a single file:

As you can see, some leechers have the check, some don't. I don't seed to the ones that have the check. When I hover over the ones with the check it says at the bottom of the hover box: "Peer wants you to upload, but you do not want to (interested and choked)."

What is strange though it doesn't happen to all torrents. Here is a screenshot from another single file torrent:

As you can see, no checks for leechers.

This did not happen with 2.22 and it does "reset" itself if I restart the application, until it does it again.

Change History (11)

comment:1 Changed 12 years ago by livings124

  • Component changed from Mac Client to libtransmission
  • Owner changed from livings124 to jordan

This value is coming straight from tr_peer_stat's isSeed.

comment:2 Changed 12 years ago by MacJunkie


Just for your info, I have been running into this exact same problem. If it's any clue, here's something I did:

1) I reverted back from 2.31 to 2.22. The offending files (with the checkmarks) came up as having no data. The torrents with NO PROBLEMS came up as still having all their data! (Strange). 2) I did "Verify Local Data" on all the offending torrents and they verified OK. 3) Then I resumed these torrents in 2.22. No checkmarks beside the leechers this time. So everything OK.

4) However, just as an experiment, I went back to 2.31. First I PAUSED all torrents in 2.22. Then I quit 2.22 and went to 2.31. All torrents showed up OK with all data. So I started a few of the "bad" torrents. Same problem. So I paused again, and went back to 2.22. 5) STRANGELY, in 2.22, the "bad" torrents I started in 2.31 came up as having no data again! So I had to re-verify them.

For now, must stick with 2.22 if I wish to seed anything. (Otherwise, there's no seeding available in 2.31 with these particular torrents). I have 6 torrents with the problem right now. Only certain torrents have this problem and only in 2.3x.

comment:3 Changed 12 years ago by livings124

The issue with data not appearing correctly from going from 2.3 to 2.2 is most likely related to 2.3 internal resume data not being compatible with older versions.

comment:4 Changed 12 years ago by jordan

possible fix in r12517

comment:5 Changed 12 years ago by jordan

  • Milestone changed from None Set to 2.32
  • Status changed from new to assigned

comment:6 Changed 12 years ago by jordan

  • Resolution set to fixed
  • Status changed from assigned to closed

Seems to be fixed.

Mac users, if you see this problem again, please reopen the ticket. Thanks!

comment:7 Changed 12 years ago by shawn

  • Cc shawn.bissell@… added
  • Resolution fixed deleted
  • Status changed from closed to reopened

Just saw exact same problem in 2.33

comment:8 Changed 12 years ago by jordan

shawn, could you provide more information? a screenshot?


comment:9 Changed 12 years ago by livings124

shawn: ping

comment:10 Changed 12 years ago by livings124

  • Resolution set to fixed
  • Status changed from reopened to closed

Please reopen with more info. It's quite possible you just saw partial seeders.

comment:11 Changed 12 years ago by shawn

Sorry I was on vacation and away from my computer that has my torrents running. Yes, I checked again and the hover info box indicated they were partial seeds. I was just confused because I thought the check mark indicated a full seed. Some documentation on the check mark and the Peers inspector would have helped.

Note: See TracTickets for help on using tickets.