Check out partner presentation from the Canonical stand at Linux World Expo

Community

Report a problem

If you think you have found a bug, you should look at the following guides before deciding whether to file a bug report or not.

When to file a bug

  • You can repeat the problem
  • It is not a feature of the programme

When to not file a bug

Actually filing the bug

So, your bug is an actual bug. The first thing you should do is check if it has already been reported by searching through the existing bugs and the release notes.

If it has not been reported, then you can report a new bug. Fill out a useful summary and select which program it happened in. If you do not know, read finding the right package or ask someone on #ubuntu-bugs on the Freenode IRC server. Then fill out the description with as much information as you can, including the version of Ubuntu you are using. It is better to have more information than too little.

Once you have filled out the package name, summary and description, click on "Submit Bug Report". When entering your initial description of the bug it is not possible to add attachments. However, after you have clicked "Submit Bug Report" it is then possible to add attachments. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done with your initial report but will mostly likely be contacted for more information about your bug.

  • File the bug on one package only. If after reading finding the right package you really don't have a clue, file it on "Ubuntu".
  • Do not file it in a release (Breezy/Dapper), just on the source package in Ubuntu.
  • For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vv" and "lspci -vvn" will help.
  • For display/X problems, always attach /etc/X11/xorg.conf and /var/log/Xorg.0.log.

NOTE: Most Kubuntu specific packages are listed here

If you need help with debugging a problem, see DebuggingProcedures.