Responses

Differences between revisions 192 and 193
⇤ ← Revision 192 as of 2008-07-22 20:53:03 →
Size: 26227
Editor: modemcable066
Comment: add a stock reply to Bugs/Responses for submitting ideas to [WWW] http://brainst
← Revision 193 as of 2008-07-22 21:07:27 → ⇥
Size: 26265
Editor: modemcable066
Comment: Improves Brainstorm Response
Deletions are marked like this. Additions are marked like this.
Line 206: Line 206:
||<tablestyle="background-color: #eee"> Thank you for taking the time to make Ubuntu better. Since your bug report describes an idea to improve ubuntu, you are invited to post your idea in Ubuntu Brainstorm at https://brainstorm.ubuntu.com/, where it can be discussed, voted by the community and reviewed by developers. Thanks for taking the time to share your opinion! || ||<tablestyle="background-color: #eee"> Thank you for taking the time to make Ubuntu better. Since what you submitted is not really a bug, or a problem, but rather an idea to improve ubuntu, you are invited to post your idea in Ubuntu Brainstorm at https://brainstorm.ubuntu.com/ where it can be discussed, voted by the community and reviewed by developers. Thanks for taking the time to share your opinion! ||

These standard responses can be used when replying to a bug report if it is ...

TableOfContents

Not described well

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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 at http://wiki.ubuntu.com/DebuggingProcedures BRBRAt a minimum, we need:BR1. the specific steps or actions you took that caused you to encounter the problem,BR2. the behavior you expected, andBR3. the behavior you actually encountered (in as much detail as possible).BRThanks!

Missing Steps to Recreate Bug

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:BRBR* Is this reproducible?BR* If so, what specific steps should we take to recreate this bug?BRBRThis will help us to find and resolve the problem.

Patch that needs some work before inclusion

To get your fix included in Ubuntu, it would help if you tried transforming it into a debdiff (http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer somebody else to do that, that's fine - please just indicate if you're available to do that.

Package or domain specific questions

The following packages or type of bugs require the specific debugging information:

Debugging Kernel General

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.BRBRPlease include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report. BR3. Please run the command "sudo 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 at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Debugging Sound Problems

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.

Debugging ACPI

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Debugging Removable Devices

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested at https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.

Debugging Hardware Detection

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Debugging USB Storage

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested at https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.

Debugging XAutoconfiguration

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.BRBRPlease include the information requested at https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.

Debugging Xorg in general

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your display and video card? Please also attach the /var/log/Xorg.0.log from this attempt. Thanks in advance.

Freeze during boot or shutdown screen

Thanks for your bug report and for your contribution to ubuntu. In order to determine if this issue is usplash related, would you boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for a single boot, you can follow these steps :BRBR1.Press Esc during Grub boot delay to access the boot menu. BR2.Select your actual Ubuntu boot line and press "e" to edit it. BR3.Select the "kernel" line and press "e" to edit it. BR4.At the end of the line, remove "splash" and "quiet" and press "enter". BR5.Type "b" to boot the custom boot line.

Debugging Live CD Installation

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.BRBRPlease include the information requested at https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments by visiting your bug's web page. Thanks in advance.

Debugging Update Manager

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as attachments? Thanks in advance.

Incomplete bugs without a response from submitter

In the event that a bug has been in the "Incomplete" state for more than 4 weeks, meaning it has not received a response to a request for more information, the bug status should be changed to "Invalid" with a comment similar to:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Bugs without a package

Sometimes bug will be reported just using the "Ubuntu" package. This is not the best place for the bug though and we should encourage bug reporters to report the bug against the correct package by pointing them at some documentation. Keep in mind PKGNAME is a variable.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in PKGNAME.

Bugs resolved after update or config change

Ocassionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to Invalid since we don't know the root cause and when closing the bug report it is a good idea to take an opportunity to let the reporter know how to manage bug statuses.

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Needing testing in the development release

A lot of bug reports need testing in the development release of Ubuntu. This is something that most anyone can do by downloading the Desktop CD, booting from it and testing their particular bug.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Intrepid Ibex. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Missing a crash report or having a .crash attachment

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.BRBRIf you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.BRBRIf you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.BRIf you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.BRBRI'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Firefox crash report that fails retrace

Firefox bug triaging policy is to close (set to "invalid") crash reports from apport that fail retracing.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Please go ahead and submit a new crash report if it crashes again with the latest available version of the package. Thanks in advance for your cooperation and understanding.

A duplicate

When making a bug report a duplicate of another it is important to communicate to the reporter that any discussion regarding the bug should take place in the master bug. Keep in mind that NUMBER is a variable and should be the number of the master bug report.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug NUMBER, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

About an obsolete version of the software for reporter's release

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, you are not using the most recent version of this package for your Ubuntu release. Please upgrade to the most recent version and let us know if you are still having this issue. Thanks in advance.

Missing a back trace

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Need valgrind log

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

A bug that should be handled upstream

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here:

Old untouched bugs

Old new bugs that haven't been touched.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Compiz is now included in main for Gutsy. However, some users may be using packages from other repositories. So the first step will be to find out which package version they have installed. In the event that it is not from the Ubuntu repository the bug should be set to Invalid.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this compiz package is not from the official Ubuntu repositories, and as such is not supported here. Please report this bug upstream at https://bugs.freedesktop.org/enter_bug.cgi?product=xorg . Thanks!

xine-lib and ffmpeg bugs

Thank you for taking the time to report this bug and helping to make Ubuntu better. You have reported a crash in the xine-lib library. In order to be able to actually fix this bug, we must be able to:BRBR1. reproduce it;BR2. check if it happens with the latest version; andBR3. understand where it actually crashes.BRBRYou can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote side that are password protected or otherwise restriced (like services like rapidshare.com and similar) are absolutely not acceptable.

Packages not provided by Ubuntu

Occasionally, bug reporters will report a bug about a version of a package not provided by Ubuntu or less often about software not provided by Ubuntu. In which case we can not help them and the bug should be set to Invalid.

Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! BRBRIf you are interested in learning more about software repositories and Ubuntu the following pages should be informative:BRBR1. http://www.ubuntu.com/community/ubuntustory/components - information about Ubuntu repositoriesBR2. https://help.ubuntu.com/community/Repositories - information regarding managing repositories

Fixed in Development release while still existing in a previous release

The bug's state should become Fix Released and if the package qualifies for a [https://wiki.ubuntu.com/StableReleaseUpdates#head-9bac29d96da353649a97b4b1918c0b382b79a000 Stable Release Update (SRU)]:

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Intrepid Ibex.BRBR This is a signficant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.BRBR[1]: https://wiki.ubuntu.com/StableReleaseUpdates#head-a7a957d3d691c2754ba24e5085481107ed703b49

The bug's state should become Fix Released and if the package does not qualify for a SRU because it is considered a minor bug and the package can be backported:

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Intrepid Ibex.BRBR If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages

The bug's state should become Fix Released and if the package can not be backported:

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Intrepid Ibex. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.

Reported by someone not respecting the Code of Conduct

Thank you 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, the majority of whom are volunteers, so please bear this in mind.

A support request

Determining whether a bug report is actually a support request can be quite challenging, but if you decide the bug is a support request you can convert it to such by clicking "Convert to a question" at the top of the bug's web page. This will mark the bug as "Invalid", create a new question in the answer tracker and link it to the bug. In the comment dialog that you receive, post a comment to inform the reporter about your action, and advise them to use the support tracker for any future problems.

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .

It is also a good idea to change the source package beforehand if it's set incorrectly, so that the question will be associated with the correct package in the answer tracker, or edit the question afterwards and assign it to the correct package. If it doesn't pertain to a specific package, change it to "Ubuntu".

Suspected bad ISO download

This response may be necessary when someone is having strange issues with the Desktop CD.

Thank you for taking the time to report this bug and helping to make Ubuntu. While we appreciate the difficulties you are facing, 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. Could you please visit https://help.ubuntu.com/community/HowToMD5SUM follow the instructions and report back as to whether or not the MD5SUM verified? Thanks in advance.

A suggestion for changing defaults

Thank you for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use.

About an incorrect translation

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, Ubuntu gets its translations from the translations portion of Launchpad (http://translations.launchpad.net/ubuntu/), where translation teams work on making Ubuntu more useful in their language. If you want to change a translation in Ubuntu there is the right place.

Firefox

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs, or upload (as an attachment) the crash report from /var/crash/.BRBRAlso, please answer these questions:BRIs this crash reproducible? If so, which are the steps that lead to it?BRWhich flash package do you have installed?BRWhich Java package do you have installed?BRWhich Firefox extensions do you have installed?BRBRThis will greatly aid us in tracking down your problem.

Upgrade problems

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please attach the files in /var/log/dist-upgrade to this bug report?BRBRThis will greatly aid us in tracking down your problem.

Incomplete Package Request

Thank you for taking the time to request this package and helping to make Ubuntu better. Unfortunately you have not provided enough information for a developer to start packaging this application. Please make sure this bug meets the guidelines at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages. An example of a complete package request is available at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages.

Triage Successful

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

An idea to improve ubuntu

Thank you for taking the time to make Ubuntu better. Since what you submitted is not really a bug, or a problem, but rather an idea to improve ubuntu, you are invited to post your idea in Ubuntu Brainstorm at https://brainstorm.ubuntu.com/ where it can be discussed, voted by the community and reviewed by developers. Thanks for taking the time to share your opinion!

Other projects have standard responses as well:

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

Bugs/Responses (last edited 2025-09-18 13:12:42 by sally-makin)