Reporting Bugs

If you think you've found a bug in the software, first make sure you're using the latest version from www.mixxx.org, then check the FAQ, the Troubleshooting page and the forums to see if there is a known solution or workaround or if other people are having the same problem.

If you don't find anything there, our bug tracking system is located at https://bugs.launchpad.net/mixxx. First try a few searches on various keywords related to the problem to see if it's already been reported and what the current status is. If you find one or more that relate, click change on "This bug doesn't affect me" to "vote" for the bug (you may need to sign in to see this.)

If no existing bugs cover your issue, please gather the following information:

Steps to reproduce the problem. Please be as detailed as you can be. For example, rather than saying "Foo doesn't work", say "When I clicked on the Bar button, Foo did not put the Bazes in the right place. I expected the Bazes to be put in Folder 1, but instead Mixxx put them in Folder 2." If you cannot write well in English, please write your description in both English and another language you are more comfortable writing in.
Operating system (Windows, Linux, OSX, etc.) and version
CPU architecture (Athlon, Core 2 Duo, Celeron, Pentium II, etc.) and speed (in MHz or GHz)
Your video and sound hardware (Brands, models, options, etc.)
Information logs

Much of the system information can be gathered from System Information in Windows (found under Control Panel->Administrative Tools->Computer Management->System Information,) and with the commands uname -a and lspci -v on Linux.

Gathering logs

Obtain the following information and add it as an attachment to your bug report:

Linux & Mac OSX

Most recent console output at the time of the error (About 50 lines or so.)
Back-traces from gdb are also extremely helpful. To capture one you need to install the gdb package (GNU Debugger), then from a console window run: gdb --eval-command=run mixxxReproduce the crash mixxx and then type thread apply all bt at the (gdb) prompt and copy the lines from your terminal and paste them into the bug report.

Windows

Mixxx.log

Find and attach this file to the bug. (Don't just paste it into the text area because it's long!) See the Troubleshooting FAQ for information on where it can be found.

Debugging Logs

If Mixxx crashes on you and you know how to reproduce the crash, please do the following:

Ensure Windows Error Reporting is enabled

Go to Start
Select Control Panel
Select Action Center
Select Change Action Center settings
Select Problem reporting settings
Select Change report settings for all users
Select Automatically check for solutions (Recommended)
Select the Ok button to apply the settings

Now collect information from the following three sources:

Debug diagnostic tool

Download & install the Microsoft debug diagnostic tool
Start Mixxx from inside the tool (or attach it to a running Mixxx process)
Make Mixxx crash
Save the output from the debugging tool to a text file and attach it to your bug report

Event logs

Go to Control Panel -> Administrative Tools -> Event Viewer
Click Application Log and System Log. Make note of what the most recent event is in both.
Start Mixxx, make it give the error
Refresh the display of both logs (F5 key) and look at any new events logged (double click them.)
Click the Copy button (looks like two pieces of paper)
Paste the text into your bug report (do this for each new event logged since you started the program.)

Windows Error Reporting

WER will automatically appear if an application crashes.

Click Send
Click View Details
Save the files to a folder of your choice
Attach the files WERxxxx.tmp.appcompat.txt and WERxxxx.tmp.version.txt to your bug report. (xxxx is some number.) Do not include the .dmp file! (You can just delete that since it's very large.)