Changes between Initial Version and Version 1 of MovedToGitHub/BugSubmission

Jan 21, 2010, 1:04:51 PM (12 years ago)



  • MovedToGitHub/BugSubmission

    v1 v1  
     1= Submitting a Bug Report =
     3If you're having trouble with Transmission then the things you should do in order are:
     4 1. Make sure you are running the current release
     5 1. Check the [FrequentlyAskedQuestions FAQ].
     6 1. Search this wiki
     7 1. For a bug, ideally we'd like you to check if it still exists in the nightly build (there are .dmgs for the Mac) - see [wiki:Downloading].
     8 1. Search the Issue Tracker to see if your concern has already been reported:
     9     * [ All open tickets]
     10     * [ Search]
     11 1. If you ''don't'' see a ticket matching your problem or feature
     12     * read the section below on '''Submitting a Bug Report'''
     13     * [ add a new ticket].
     14   If you ''do'' see an existing ticket, please add a comment there again adding as much information as possible.
     15   The more users interested in a ticket, the higher priority it's given.
     19== Information Required in a Bug Report ==
     20 * State the version of Transmission you're using (eg Linux/GTK+ 1.80).[[BR]]
     21   If you're using a GUI version of Transmission, you can find its version in the `About' dialog in the Help menu.[[BR]]
     22   '''Don't''' say ''the latest version'' it's ambiguous.
     23 * State what operating system and version (eg Mac OS X 10.5.8, Ubuntu 8.04, ...)
     24 * Describe the symptoms in a short precise manner.
     25 * If the problem is reproducible and you explain how to reproduce it, then it stands a high chance of being addressed.
     26   If the problem is intermittent then we still want to know, but if you can't tell us how to reproduce it we can't easily work on it.
     27 * See if the problem only occurs under certain conditions.[[BR]]
     28   Eg: If you're seeing the bug with 50 torrents running and speed limits turned on, see if it persists with speed limits turned off.[[BR]]
     29   See if it persists with 1 torrent running. See if it persists after pausing and restarting the torrent. etc.[[BR]]
     31'''The more work you do to narrow down the bug, the more chance we have of finding and fixing it.'''
     33== Reporting specific types of problems ==
     35Additional information or steps are required for certain categories of problem:
     37=== Slow Speeds ===
     38If you're experiencing slow speeds and you've been through the wiki and [FrequentlyAskedQuestions FAQ] then you need to provide the following information '''in addition''' to that above:
     39 * Do you have any per-torrent or global speed limits set?
     40 * What are your global and per-torrent peer limits?
     41 * How many seeds and peers does the `Peers' tab say there are in the swarm?
     42 * How long ago does the `Tracker' tab say the last announce and scrape results were?
     43 * In the `Tracker' tab's list of trackers, how many Tiers are there, and how many trackers are listed for each tier?
     44 * How many peers are you connected to?
     45 * Has your torrent finished downloading?
     46 * If you're still downloading, do any of the connected peers have a higher "completed" percentage than you?
     47 * Is your incoming peer port open or closed?[[BR]]
     48   The 'Peers' and 'Tracker' tabs are in the dialog named "Inspector" on the Mac GUI and "Torrent Properties" on the GTK+ GUI.
     50=== Crash on the Mac ===
     52  If you have problems on the Mac version then please do these extra steps:
     54  * Make sure your system is updated to the latest version of your operating sytem. Note As of 1.60 Transmission requires Mac OS X 10.5 or later.
     55  * If you're running a nightly build, set the language to English. The localizations will sometimes crash the nightly builds until they are updated right before an official release.
     56  * OS X collects two pieces of crash information that can help us fix the crash:
     57    1. In, look under LOG FILES > ~/Library/Logs/ > CrashReporter > for Transmission. If you find one, include it in your forum post.
     58    2. In, select LOG DATABASE QUERIES > Console Messages, and search for Transmission. If you find a message that mentions an assertion failure, include it in your forum post.
     60If these two pieces of information above are too large for your forum post, Paste them [ here], click the "one month" and "send" buttons, and include the pastebin's URL in your forum post.
     62=== Port Mapping Error ===
     64Read the [PortForwardingGuide Port Forwarding Guide] first.
     65You then need to include:
     66  * what router you're using
     67  * that you've confirmed that either UPnP or NAT-PMP is enabled on it
     68  * If you're using a custom firmware, tell us which one
     69  * Most importantly, post the lines from the Message Log that contain the phrase "Port Mapping". They will look something like this:
     71          02:12:27 Port Mapping (NAT-PMP): initnatpmp returned success (0)
     72          02:12:27 Port Mapping (NAT-PMP): sendpublicaddressrequest returned success (2)
     73          02:12:27 Port Mapping: mapping state changed from 'not mapped' to 'mapping'
     74          02:12:27 Port Mapping: opened port 55555 to listen for incoming peer connections
     75          02:12:35 Port Mapping (NAT-PMP): readnatpmpresponseorretry returned error -7, errno is 111 (Connection refused)
     76          02:12:35 Port Mapping (NAT-PMP): If your router supports NAT-PMP, please make sure NAT-PMP is enabled!
     77          02:12:35 Port Mapping (NAT-PMP): NAT-PMP port forwarding unsuccessful, trying UPnP next
     78          02:12:37 Port Mapping (UPNP): Found Internet Gateway Device ''
     79          02:12:37 Port Mapping (UPNP): Local LAN IP Address is ''
     80          02:12:37 Port Mapping (UPNP): Port forwarding via '', service 'urn:schemas-upnp-org:service:WANIPConnection:1'. (local address:
     81          02:12:37 Port Mapping (UPNP): Port forwarding successful!
     82          02:12:37 Port Mapping: mapping state changed from 'mapping' to 'mapped'