Revision 57 as of 2008-07-29 21:44:18

Clear message



The proper source package

Assigning bugs to packages helps direct bug reports to the developer(s) most likely to be able to help. By ensuring that this information is accurate, you can increase the chances of the bug being fixed promptly. Often, it is unclear which package contains the bug, and in these cases it is appropriate to file the bug in Ubuntu. If a bug is assigned to a package which is clearly not correct, and you don't know the correct package, change it to Ubuntu. Some hints on finding the right package can be found in ["Bugs/FindRightPackage"].

The correct package for bugs in the Linux kernel is dependent upon the release of Ubuntu being used.

  • For Dapper (6.06) the correct package is linux-source-2.6.15
  • For Edgy (6.10) the correct package is linux-source-2.6.17
  • For Feisty (7.04) the correct package is linux-source-2.6.20
  • For Gutsy (7.10) the correct package is linux-source-2.6.22

Confirming problems

If a bug is marked as New, it is helpful for you to try to reproduce the problem, and record the results in Launchpad. If you are able to confirm the problem, you may change the status to Confirmed. If you are unable to confirm the problem, that is also useful information which should be recorded in a comment. When confirming the bug be sure to indicate which version of the package you used. One way to get the package version is via 'dpkg -l $pkgname' where $pkgname is the name of the package you are testing. Do not confirm your own bugs - confirmation is required from someone other than the original reporter.

Forwarding bugs upstream

You should forward bugs to the authors of the software (upstream), if

  • you made sure that the bug doesn't occur because of Ubuntu related changes,
  • the bug report is complete.

To learn how to do this, please consult [ The Forwarding section in the How to Triage Page].

How to deal with Feature Requests

If you feel that the bug reported is a non-trivial feature request disguised as a bug report, please introduce the reporter gently to the Specification Process we have. Be sure to mention the following specification resources; FeatureSpecifications, SpecSpec, ["SpecTemplate"] and

How to deal with Support Requests

If you feel that the bug reported is a support request disguised as a bug report, please gently introduce the reporter to the Support Tracker located at .

How to deal with suggestions for changing defaults

If you feel that the bug reported is a suggestion for changing defaults disguised as a bug report, please kindly reroute the discussion to an appropriate mailing list or a discussion forum. If this has already been discussed and rejected, explain the reasons to the user and direct them to the corresponding discussion for further suggestions/comments.


Reminder of the Code of Conduct

Note that the Code of Conduct applies to conversations in bug reports too. So if you observe people being disrespectful, please direct them to

Setting Status

Include(Bugs/Status, , from="^KBHeader", to="^----" )

Setting Importance

Include(Bugs/Importance, , to="^----")


Don't change this field unless specifically instructed by a developer. In particular, do NOT use this field to record the release of Ubuntu in which the bug was observed: that is not its purpose! It is used by the release team when there is a reason to address the bug in a specific milestone release.

Old Bugs

In many cases bugs reported in earlier versions are still open in our bug tracking system. They may have been fixed upstream without it being noted in Launchpad or the design may have changed so that the issue is no longer relevant. If the bug does not represent a security issue or is otherwise critical, it is very unlikely that the fix will be back-ported to older versions of Ubuntu. When it is fixed in the development branch it is therefore most appropriate to mark it 'Fix Released'. This helps clear the bug tracking system for old cruft.

Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]