Version 5 (modified by Cas, 9 years ago) (diff)

add more info

Before Reporting a Bug

  • Install the latest stable version: 2.1.1

Search for Existing Issues

Other bug trackers relating to Deluge:

libtorrent (rasterbar) Bugs:

Ask your Question Effectively

Two links that provide helpful generic tips for reporting software problems.

How To Ask Questions The Smart Way
How to Report Bugs Effectively

Collect Bug Information

You will need some/all of the following information when reporting a bug:

Note: If you are using Client and Daemon you may need version or logs from both.

  • Version Information:
    • Deluge
    • libtorrent
    • Operating System
    • Browser (if using WebUI)
    • Plugins Enabled
    • Language in use (i.e. if not English)
  • Installation type: source, package or installer
  • Precise steps to reproduce the bug.
  • Debug Logs or copies of any errors or traces.
  • Config files.
  • Screenshots and screencasts can be helpful for GUI issues.

Hard crashes of deluge

A backtrace using gdb may be required for hard crashes of Deluge (crashes without an obvious error). Here is a deluged example:

   gdb --args python /usr/bin/deluged -d
   (gdb) run
   ## After Crash ##
   (gdb) thread apply all backtrace

Opening a Bug Ticket

The bug ticket system we use is called Trac. Sign up if you haven't already.

Note: The Trac user account is separate to the Forum user account.

  1. Create a new bug ticket
  2. Fill in the boxes, making sure the following are completed:
    • Summary: Short description of issue
    • Description: Include the steps to reproduce and other collected information, use {{{ }}} markup for pasting code or errors.
    • Version: Deluge version
    • Component: Best guess as to where the problem occurs
  3. Attach any logs, screenshots or patches