Ubuntu Wiki

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!

Thank you for the bug report. Also, please answer these questions:BRBR* Is this crash reproducible?BR* If so, which are the steps that lead to it?BRBRThis will greatly aid us in tracking down your problem.

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have 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 at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

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 information requested from https://help.ubuntu.com/community/DebuggingSoundProblems as separate attachments.

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 information requested from https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

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 information requested from https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.

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 information requested from https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

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 information requested from https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.

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 information requested from https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.

We are closing this bug report as it lacks the information, 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.

Thanks for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is missing. Could you please add the crash report that you received? It will be found in '/var/crash/'. This will allow us to better troubleshoot your bug. Thanks in advance.

Thanks 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 and is being marked as such. Please feel free to report any other bugs you may find.

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.

Thanks 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 software package. Please upgrade to the most recent version and let us know if you are still having this issue.

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.

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

Thanks for taking the time to report this bug and helping to make Ubuntu better. However, this beryl package is not from the official Ubuntu repositories, and as such is not supported here. Please report this bug upstream at http://bugs.beryl-project.org/ . Thanks!

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 Edgy Eft 6.10, please follow the instructions for "How to request new packages". <https://help.ubuntu.com/community/UbuntuBackports#request-new-packages>

Thanks for the bug report. I'm closing it because the bug has been fixed in Feisty. It won't be fixed in Edgy Eft 6.10 because the bug doesn't fit requirements for backporting. See <https://help.ubuntu.com/community/UbuntuBackports> for more information.

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.

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>

Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. <https://answers.launchpad.net/questions>

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>

Thanks 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/community/forums/> might be a good start.

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.

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 information requested from https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments.

Thank you for the bug report. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs, or upload 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.