If you've come here when trying to file a bug about Ubuntu in Launchpad this was deliberate. Please read the following documentation regarding how to report a bug about Ubuntu.

Reporting bugs

Ubuntu uses Launchpad to keep track of bugs and their fixes. To file a bug you first need to create an account. Once you have an account you can use the tools we've provided you on your Ubuntu system to file bug reports.

Note 1: If you use Kubuntu, please see the Kubuntu variant of this page here.

Note 2: After the bug is reported, please always leave the Status set to New (Curious about bug status? Details here).

Filing a bug with ubuntu-bug

Ubuntu 8.10 and later

Press Alt+F2 to open the "Run Application" window, pictured above. Type ubuntu-bug <package name> and click Run. Server Edition users should use a terminal instead. If you're not sure which package has a problem, refer to the instructions for finding the right package.

To file a bug against a program that is currently running, go to System > Administration > System Monitor, and find the ID of the process. Server Edition users should use ps aux.

Then type the process ID instead of the package name into the "Run Application" window.

Ubuntu 8.04 LTS to Ubuntu 9.04

In Ubuntu 8.04 LTS, you need to type ubuntu-bug -p (lowercase p) when reporting a bug about a package, or ubuntu-bug -P (capital P) when reporting a bug about a process ID. Instructions are otherwise identical to the above.

Ubuntu 9.10 and Later

You only need to type ubuntu-bug PKGNAME when reporting against a package, or ubuntu-bug PID when reporting a bug about a process ID. Instructions are otherwise identical to the above.

Filing bugs when off-line

In the event that you have a bug with your internet connection or want to file a bug for another system you can still do this using apport. Using the command apport-cli -f -p <package name> on the target system will collect information and provide you with an option to "K: Keep report file for sending later or copying to somewhere else". The report is then saved on the target system, in your /tmp directory which is cleared out on reboot, with a .apport extension. After copying it to a different system you can file that report using ubuntu-bug  <location of apport file>.

Filing bugs at Launchpad.net

If for some reason you cannot file a bug through the Apport tool you can file one via Launchpads own bug report form. When doing so it is best if you have determined which package it should be filed against. Read 'finding the right package' for guidance or use Launchpad's package search feature.

To file a bug against a specific package you can also use a URL like the following:

• http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect

where PACKAGENAME is the name of the source package about which you want to file the bug. In the event that you want to request a piece of software be packaged for Ubuntu please follow the instructions in the wiki.

Using the help menu in the affected application

Note: Since 10.04 this only works for the Development Releases, If you're running Lucid you might want to use the ubuntu-bug method. (See Lucid/BugHandling for information on this change.)

If you want to report a bug on an application that is running and responding, use the application's help menu: Help -> Report a problem.

This method is preferable to filing a bug at the Launchpad website - it automatically attaches relevant information, which helps analyze the problem.

If an application crashes, and you're using a version of Ubuntu which is actively under development, Apport will start automatically, raising an appropriate bug report for you to complete in Launchpad. This provides developers with rich debugging information that will make it easier to fix the problem.

Filing translation bugs

All translation issues should be filed against the Ubuntu Translations project (ubuntu-translations). From there the bugs will be triaged and assigned to the right person and package.

Here is a non-exhaustive list of problems that are appropriate for the Ubuntu Translations project:

• Wrong translations or spelling mistakes in applications
• Errors in spellcheckers or language support

• A string from an application is not available for translation in Launchpad Translations

• An application from the Ubuntu main repository is not available for translation in Launchpad Translations

• A translation made in Launchpad Translations is not updated in the Ubuntu language packs

• There is a duplicate translation template (the same application can be translated in two different places) in Launchpad Translations

• A template/translation is no longer used in Ubuntu and should be disabled from Launchpad Translations

You can also consult the current bugs to see the big picture. In case of doubt, you can always contact the Translations team.

Adding Apport Debug Information to an Existing Launchpad Bug

If you have already reported a bug directly via Launchpad, but want to add additional debugging information via Apport to the bug, you can do this by running the command apport-collect bug_number via "Run Application" or terminal window. If this fails then run apport-collect -p <package name> bug_number.

Writing a useful report

When a developer fixes a bug, they will test that the bug occurs, make a small change to the program, then see if the bug has gone away. Depending on the bug, they might need to run the same test dozens or hundreds of times. When you submit a bug report, it's important to specify three things:

1. What you expected to happen
2. What actually happened
3. The minimal series of steps necessary to make it happen, where step 1 is "start the program"

Fill in the description field with as much information as you can, including the release of Ubuntu you are using and steps for someone else to recreate the bug. It is better to have too much information in the description than not enough.

Only describe a single problem per bug report so that each can be followed up on in detail. If you experience several issues file separate reports.

Add supporting attachments to explain or help others reproduce your bug. This might include a screenshot or video capture of the problem or a sample document that triggers the fault. To add an attachment to the bug use the Include an attachment section of the bug form. Additional attachments, if necessary, can be added after the bug is reported via Add a comment/attachment at the bottom of the page.

For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vvnn" and "dmesg", after a fresh boot, will help a lot.

Back to top

When not to file a bug

• Requesting new software you should follow the guidelines in https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages

• Support requests should go to support requests in Launchpad, the Ubuntu forums, the #ubuntu channel on the Freenode IRC server, or the ubuntu-users mailing list.

• Feature and policy discussions (including suggestions to change defaults) should be discussed on the ubuntu-devel-discuss mailing list.

• Development ideas should be posted to http://brainstorm.ubuntu.com/ or discussed on the ubuntu-devel-discuss mailing list.

• Already filed - Please check if it has already been reported by searching through the existing bugs and the release notes for your release of Ubuntu: 6.06 (Dapper Drake), 8.04 (Hardy Heron), 8.10 (Intrepid Ibex), 9.04 (Jaunty Jackalope), 9.10 (Karmic Koala),10.04 (Lucid Lynx) . If you have further information about an already reported bug, add this information to the existing reported bug, instead of opening a new one.

Back to top

Getting advice

If you need help in finding the right package or providing appropriate information ask someone on #ubuntu-bugs on the Freenode IRC server or on the bugsquad mailing list.

Back to top

Other languages

• Spanish

• Romanian

Back to top

See Also

• A screencast on using these tools by Daniel Holbach

• How to Report Bugs Effectively, by Simon Tatham

• Debugging Procedures

Back to top