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 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 hosted on Launchpad. 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 to report a new bug on Launchpad.
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.
Obtain the following information and add it as an attachment to your bug report:
On Ubuntu, if Mixxx crashes and Ubuntu asks if you would like to report the problem, please click report. We receive these crash reports, and they are quite useful.
If you are filing a bug, see if you have a crash report, stored in
/var/crash, and if you find one for Mixxx, please attach it to your bug report. If you don't find an error report, please use the
ubuntu-bug tool to create an error report. From a terminal, or by pressing
Alt + F2 to invoke the run dialog, enter:
ubuntu-bug mixxx --save mixxx.crash
This will create a mixxx.crash file in your home directory which you can attach to the bug report you file on our Bug Tracker. However, since this isn't a crash from an actual run of Mixxx, it will not contain details on your specific bug – just background information about your system that will be useful to us. If you are reporting a crash bug, it would be useful if you could include a crash report from
/var/crash from a time when Mixxx actually crashed. Additionally, see below about generating backtraces. Crash reports sometimes include backtraces, but if you collect one yourself it may be more informative.
gdb --eval-command=run mixxx
Reproduce 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.
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.
If Mixxx crashes on you and you know how to reproduce the crash, please do the following:
Now collect information from the following three sources:
WER will automatically appear if an application crashes.