| 1 | |
| 2 | = Before Reporting a Bug = |
| 3 | |
| 4 | * Make sure you are using the latest stable version: '''[[Include(http://download.deluge-torrent.org/version)]]''' |
| 5 | * Check the '''[wiki:Faq FAQ]''' |
| 6 | |
| 7 | == Search for existing Issues == |
| 8 | |
| 9 | * '''[search: Deluge Bugs]''' |
| 10 | * '''[http://forum.deluge-torrent.org/search.php Forum]''' |
| 11 | * Site search using [https://www.google.co.uk/search?q=site:deluge-torrent.org Search Engine] |
| 12 | |
| 13 | ''' Distribution Bugs for Deluge:''' |
| 14 | |
| 15 | * [https://bugs.launchpad.net/ubuntu/+source/deluge Ubuntu] |
| 16 | * [https://admin.fedoraproject.org/pkgdb/acls/bugs/deluge Fedora] |
| 17 | * [http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=deluge Debian] |
| 18 | * [https://bugs.archlinux.org/index.php?string=deluge Arch] |
| 19 | * [https://bugs.gentoo.org/buglist.cgi?quicksearch=deluge Gentoo] |
| 20 | * [http://trac.macports.org/query?status=assigned&status=new&status=reopened&order=priority&port=deluge MacPorts] |
| 21 | |
| 22 | '''[http://www.rasterbar.com/products/libtorrent/ libtorrent (rasterbar)] Bugs:''' |
| 23 | |
| 24 | * [http://code.google.com/p/libtorrent/issues/list Official libtorrent issue tracker] |
| 25 | * [https://bugs.launchpad.net/ubuntu/+source/libtorrent-rasterbar Ubuntu (libtorrent)] |
| 26 | * [https://admin.fedoraproject.org/pkgdb/acls/bugs/rb_libtorrent Fedora (libtorrent)] |
| 27 | * [http://trac.macports.org/query?status=assigned&status=new&status=reopened&order=priority&port=libtorrent-rasterbar MacPorts (libtorrent)] |
| 28 | |
| 29 | = Collect Bug Information = |
| 30 | |
| 31 | You will need most of the following information when reporting a bug: |
| 32 | |
| 33 | ''Note: If you are using Client and Daemon you may need information from both.'' |
| 34 | |
| 35 | * Version Information: |
| 36 | * Deluge |
| 37 | * [wiki:Faq#HowdoIfindwhatlibtorrentversionIamusing libtorrent] |
| 38 | * Operating System |
| 39 | * Browser ''(if using WebUI)'' |
| 40 | * Steps involved to reproduce the bug |
| 41 | * Installation type: source, package or installer |
| 42 | * [wiki:Faq#EnableDelugeLogging Debug Logs] or the full output of any errors |
| 43 | * Screenshots can be helpful for gui issues |
| 44 | * Backtrace using gdb may be required for hard crashes of Deluge (crash without error). Here is a ''deluged'' example: |
| 45 | {{{ |
| 46 | gdb --args python /usr/bin/deluged -d |
| 47 | (gdb) run |
| 48 | ## After Crash ## |
| 49 | (gdb) backtrace |
| 50 | }}} |
| 51 | |
| 52 | |
3 | | 1. Sign up to trac if you haven't already: http://dev.deluge-torrent.org/register |
4 | | 1. Go to: http://dev.deluge-torrent.org/newticket |
5 | | 1. Enter in which version of deluge you're using |
6 | | 1. Also mention what OS you are using (and which browser if it's a bug with the web UI) |
7 | | 1. Mention how to reproduce the error |
8 | | 1. Attach any debug logs |
| 55 | The bug ticket system we use is called Trac. [/register Sign up] if you haven't already. |
| 56 | |
| 57 | ''Note: The Trac user account is separate to the Forum user account.'' |
| 58 | |
| 59 | 1. [/newticket Create a new bug ticket] |
| 60 | 2. Fill in the boxes, making sure the following are completed: |
| 61 | * ''Summary:'' Short description of issue |
| 62 | * ''Description:'' Include the steps to reproduce and other collected information, use `{{{ }}}` markup for pasting code or errors. |
| 63 | * ''Version:'' Deluge version |
| 64 | * ''Component:'' Best guess as to where the problem occurs |
| 65 | 3. Attach any logs, screenshots or patches |
| 66 | |