# FAQ:Bugs

From Audacity Development Manual

< Back to: FAQ:Errors

|< Index of Frequently Asked Questions

## "I found a bug! now what?"

The most important things when reporting a bug are to be as specific as possible and check first in the Release Notes if we already know about the problem.

If the bug is not known about, please give us enough information that we can reproduce the bug ourselves on the correct operating system. Otherwise it is unlikely that we will be able to fix it.

Please include the following essential information in your report:

- Your exact three-section version number of Audacity (for example, 2.0.0) - you can check this at Help > About Audacity or Audacity > About Audacity on a Mac computer
- The exact operating system you are using (for example, Windows 10 Home, macOS 10.14.4, Linux Ubuntu 11.10)
- Any other information about your computer and its audio connections that might be relevant (for example, 2 GB RAM, 2.2 GHz, M-Audio Fast Track USB interface).

If you can make the problem happen consistently, tell us the exact sequence of events, step-by-step from launch of Audacity that causes the bug to occur.

If you see an error message, be sure to send us the exact text of the error message, or attach an image. If you are on Mac or Linux a crash report is useful too.

When you have your bug report ready, please post to our forum.

back to top

## "Feature X is not good enough or is missing"

You can send your ideas for new or improved features to our forum. Again, be as specific as possible, and feel free to suggest your preferred way of achieving the functionality you desire.

If you are a C++ programmer, you can send us a patch or preferably a Git pull request for the bug fix or new feature.

Thanks for all your reports, suggestions and patches! All of these help us make Audacity better.

back to top

< Back to: FAQ:Errors

|< Index of Frequently Asked Questions