Responses
These standard responses can be used when replying to a bug report if it is ...
Not described well
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.BRBR We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks! |
For bugs marked Needs Info without a response from submitter:
We are closing this bug report as it lacks the information, which was described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. |
Kernel bugs
Kernel bugs are "special cases" and as such should include certain specific information before they are to be referred to the kernel team. The status of the bug should be set to "Needs Info" rather than "Rejected" in this case. Once the necessary information (log files mentioned below) are collected, please follow the instructions on the DebuggingKernelProblems page.
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: BR1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.BR2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report. BR3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.BRBRFor your reference, the full description of procedures for kernel-related bug reports is available here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks! |
About an obsolete version of the software
Thanks for the bug report. However, the version you are using is no longer maintained. Please upgrade to the most recent version, and reopen this bug report if the problem persists. |
Missing a back trace
Thanks for your bug report. Please try to obtain a backtrace <http://wiki.ubuntu.com/DebuggingProgramCrash> and attach the file to the bug report. This will greatly help us in tracking down your problem. |
A duplicate
Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find. |
OR
Thanks for the bug report. This particular bug has already been reported, but the previous report is missing information that you might be able to provide. Please look at the other bug report and answer the questions if you can. |
A bug that should be handled upstream
Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: |
Fixed in Feisty while still existing in Edgy
If the package can be backported:
Thanks for the bug report. I'm closing it because the bug has been fixed in Feisty.BRBR If you need a fix for the bug in 6.10, please follow the instructions for "How to request new packages". <https://wiki.ubuntu.com/UbuntuBackports> |
If not:
Thanks for the bug report. I'm closing it because the bug has been fixed in Feisty. It won't be fixed in 6.10 because the bug doesn't fit requirements for backporting. See <https://wiki.ubuntu.com/UbuntuBackports> for more information. |
Reported by someone not respecting the Code of Conduct
Thanks for your bug report. To maintain a respectful atmosphere, please follow the code of conduct. <http://www.ubuntu.com/community/conduct/> Bug reports are handled by humans, so please bear this in mind. |
A non-trivial feature request
For work that needs planning:
Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https://launchpad.net/ubuntu/+specs>, and if so, contact the specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https://wiki.ubuntu.com/FeatureSpecifications> |
A support request
Thanks for your comments. This does not appear to be a bug report and are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. <http://launchpad.net/support> |
Suspected bad ISO download
Thanks for your comments. We appreciate the difficulties you are facing, but it would appear that the CD image (ISO file) you downloaded could be corrupt. There is an easy way to verify the integrity of the Ubuntu ISO files you download. For more information, please visit <https://help.ubuntu.com/community/HowToMD5SUM> |
A suggestion for changing defaults
Thanks for your suggestion. The changes you are requesting require more discussion, which should be done on an appropriate mailing list or forum. <http://www.ubuntu.com/community/forums/> might be a good start. |
About an incorrect translation
Thanks for your comment. Ubuntu gets its translations from Rosetta <http://launchpad.net/rosetta>, where translation teams work on making Ubuntu more useful in their language. If you want to change a translation, Rosetta is the right place. |
A packaging request for new software not already in Debian
Thanks for your suggestion, but this is not the right place to request new software. Please add your suggestion to the wiki. <https://wiki.ubuntu.com/MOTU/Packages/Candidates> |
Links
Other projects have standard responses as well:
Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]