Responses

Differences between revisions 328 and 329
Revision 328 as of 2011-05-19 18:24:59
Size: 41164
Editor: c-98-246-63-231
Comment: Removing redundnat xorg autoconfig reply
Revision 329 as of 2011-05-19 18:28:10
Size: 41173
Editor: c-98-246-63-231
Comment: Distros aren't EOL but Releases are
Deletions are marked like this. Additions are marked like this.
Line 300: Line 300:
== Distro has reached EOL ==

If the distro has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (Note DISTRO and DATE are placeholders):

||<tablestyle="background-color: #eee">Thank you for reporting this bug to Ubuntu. DISTRO reached EOL on DATE.<<BR>>Please see this document for currently supported Ubuntu releases:<<BR>>https://wiki.ubuntu.com/Releases <<BR>><<BR>>I've tried recreating this bug with DISTRO and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.<<BR>><<BR>>Please feel free to report any other bugs you may find. ||

== Release has reached EOL ==

If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (Note RELEASE and DATE are placeholders):

||<tablestyle="background-color: #eee">Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<<BR>>Please see this document for currently supported Ubuntu releases:<<BR>>https://wiki.ubuntu.com/Releases <<BR>><<BR>>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.<<BR>><<BR>>Please feel free to report any other bugs you may find.||

information_little.png This page is part of the Bug Squad’s KnowledgeBase - pages with information about how to triage bugs.

These standard responses among with other amazing scripts are also available as a Firefox extension in a PPA at:

https://launchpad.net/~gm-dev-launchpad/+archive/ppa

When you update one of these responses, you should also update the response used by the Firefox extension. These responses can be found in the bazaar branch lp:ubuntu-qa-tools in the file gm-xml-files/bugsquad-replies.xml. To check out a branch, use

bzr branch lp:ubuntu-qa-tools

Only members of bug-control can commit to this branch, but you can submit a merge proposal and Brian Murray will review/merge it (see this email message).

And they can be used when replying to a bug report if it is ...

Contents

    1. Not described well
    2. Missing Steps to Recreate Bug
    3. Missing Apport Information
    4. Package or domain specific questions
      1. Debugging Kernel General
      2. Debugging Sound Problems
      3. Debugging ACPI
      4. Debugging Removable Devices
      5. Debugging Printing problems
      6. Debugging Hardware Detection
      7. Debugging USB Storage
      8. Debugging Xorg in general
      9. Freeze during boot or shutdown screen
      10. Debugging Live CD Installation
      11. Debugging A Distribution Upgrade
      12. Debugging GNOME Power Manager
      13. Debugging Network Manager
      14. Debugging Firefox
        1. Firefox crash report that fails retrace
      15. Debugging Samba
        1. Samba as a client
        2. Samba as a server
        3. Install/upgrade failure
      16. Debugging Openldap
        1. SSL connections failure
      17. Debugging ffmpeg (mostly libavcodec and libavformat bugs)
      18. Debugging SCIM related issues
    5. Incomplete bugs without a response from submitter
    6. Bugs without a package
    7. Bugs resolved after update or config change
    8. Needing testing in the development release
    9. Missing a crash report or having a .crash attachment
    10. A duplicate
    11. About an obsolete version of the software for reporter's release
    12. Missing a back trace
    13. Unusable stack trace after retracing
    14. Need valgrind log
    15. A bug that should be handled upstream
    16. Old untouched bugs
    17. Packages not provided by Ubuntu
      1. Packages provided by Medibuntu
    18. Fixed in Development release while still existing in a previous release
    19. Reported by someone not respecting the Code of Conduct
    20. A support request
    21. Not reported in English
    22. Suspected bad ISO download
    23. A suggestion for changing default applications or preferences
    24. About an incorrect translation
    25. Incomplete Package Request
    26. Triage Successful
    27. Triage Unsuccessful: Back to New/Incomplete Status
    28. Release has reached EOL
    29. An idea to improve Ubuntu
    30. Patch attachment not flagged as a patch
    31. Attachment incorrectly flagged as a patch
    32. Package installation failure
    33. Security Bugs
      1. Not Security
    34. Invalid One Hundred Paper Cuts
    35. Added Bugwatch
    36. Links
  1. Other languages

Not described well

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug 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.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

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:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Missing Apport Information

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

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. We need some more information from you before we can start working on this bug.

Please run the following command which will attach necessary information:

apport-collect BUGNUMBER
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` BUGNUMBER
if you are using Hardy Heron (8.04)

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

Pleas also see the specific responses for kernel bugs.

Debugging Sound Problems

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.

If you are using Karmic or later this information can be gathered for you automatically using the command apport-collect -p alsa-base BUGNUMBER where BUGNUMBER is the number of the bug you've reported.

Debugging ACPI

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please 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. We need some more information from you before we can start working on this bug.

Please include the information requested at https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.

Debugging Printing problems

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please include the information requested at https://wiki.ubuntu.com/DebuggingPrintingProblems as separate attachments.

Debugging Hardware Detection

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please 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. We need some more information from you before we can start working on this bug.

Please include the information requested at https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.

Debugging Xorg in general

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please run the command 'apport-collect BUGNUMBER' which will attach necessary information for debugging this as an Xorg problem. 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, please boot your computer with usplash disabled and then shutdown to see if you can reproduce the issue? To disable usplash for a single boot, follow these steps:

1. Hold Esc during Grub boot delay to access the boot menu.
2. Select your actual Ubuntu boot line and press "e" to edit it.
3. Select the "kernel" line and press "e" to edit it.
4. At the end of the line, remove "splash" and "quiet" and press "enter".
5. Type "b" to boot the custom boot line.

For Karmic and subsequents releases users :

Thanks for your bug report and for your contribution to Ubuntu. In order to determine if this issue is plymouth related, please boot your computer with plymouth disabled and then shutdown to see if you can reproduce the issue? To disable plymouth for a single boot, follow these steps:

1. Hold Right-Shift during Grub boot delay to access the boot menu.
2. Select your actual Ubuntu boot line and press "e" to edit it.
3. Select the "linux" line and at the end of the line, remove "splash" and "quiet".
5. Type "ctrl + x" 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.

Please 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 A Distribution Upgrade

DebuggingUpdateManager

Thanks 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 separate attachments? Thanks in advance.

Debugging GNOME Power Manager

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please run "apport-collect BUGNUMBER" from the terminal? You might also want to take a look at the debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager and submit any other logs related to your problem. Thanks in advance.

Apport will add the output of the upstream script "gnome-power-bugreport.sh" and "devkit-power --dump." "gnome-power-bugreport.sh" also includes the output of devkit-power --dump.

Debugging Network Manager

If a network-manager bug report is about not being able to connect the title or summary should be in the format: [CHIPSET] cannot connect to (ENCRYPT_METHOD) where the CHIPSET is the wireless driver used and ENCRYPT_METHOD is the encryption method used by your wireless network.

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 bug report didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, do not hesitate to ask for more assistance. Thanks in advance.

Debugging 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? Also, please answer these questions:
Is this crash reproducible? If so, which are the steps that lead to it?
Which flash package do you have installed?
Which Java package do you have installed?
Which Firefox extensions do you have installed?

This will greatly aid us in tracking down your problem.

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.

Debugging Samba

Samba as a client

Use this reply if an Ubuntu system cannot access a remote samba/windows share.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-client.

Samba as a server

Use this reply if remote clients cannot access a share provided by an Ubuntu system.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-server.

Install/upgrade failure

Use this reply if there is a package installation/upgrade failure on the Ubuntu system.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-pkg-fail.

Debugging Openldap

SSL connections failure

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. 

Please include the information requested at https://wiki.ubuntu.com/DebuggingOpenldap#ssl-client-failure.

Debugging ffmpeg (mostly libavcodec and libavformat bugs)

Thank you for taking the time to report this bug and helping to make Ubuntu better. You have reported a crash that actually happened in the libavcodec or libavformat library. In order to be able to actually fix this bug, we must be able to:

1. Reproduce it;
2. Check if it happens with the latest version; and
3. Understand where it actually crashes.

You 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 sites that are password protected or otherwise restricted (services like rapidshare.com) are absolutely not acceptable. If your file is too large, try to reproduce with the first few MB only. See http://ffmpeg.org/bugreports.html section "Submitting Sample Media" for guidelines.

Please also make sure that your file crashes with the commandline application ffplay from the ffmpeg package. If the crash does not happen with that tool, the bug does not belong to the ffmpeg package, but to some higher-level package like libxine1-ffmpeg or gstreamer0.10-ffmpeg (depending on what player has been used)

Thank you for taking the time to report this bug and helping to make Ubuntu better. In order to determine the cause of this issue, we would need some additional information.

Please post or attach the following:
1. the output of 'dpkg -l | grep scim'
2. the output of 'im-switch -l'
3. the files '/etc/scim/config', '/etc/scim/global' and '~/.scim/config'

Additionally, please answer the following questions:
1. Is this bug reproducible? (always/sometimes/no)
2. If you can reproduce the bug, what are the steps to do so?
3. Which desktop environment are you using? (Gnome/KDE3/KDE4)
4. If you remove '~/.scim/config', '~/.scim/global' and restart your X session by logging out and in again, does this bug still appear?
5. If you reinstall the 'scim', 'libscim8c2a', 'scim-bridge-agent' and 'scim-bridge-client-{gtk|qt4}' packages, followed by the procedure described in 4., does the bug still appear?

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, please send a gentle reminder with something like:

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

If, after an additional 2 weeks, the reporter still hasn't responded and there is no way someone can work with the bug, 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 bugs 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 placeholder.

Warning /!\ If you use this response, you must assign a package. If you do not know what package to assign, please leave the bug alone, and ask for help.

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.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Bugs resolved after update or config change

Occasionally 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. 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. Please 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.

Before using this, please check "rmadison <package>" to see if the package version has changed between when the bug was reported and the current development release. If it has not changed, there is no need to ask. If it has changed, check the changelog (via aptitude changelog $PKGNAME) to see if this issue has been specifically addressed.

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 - Oneiric Ocelot. 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.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'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.

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 placeholder 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, according to this report, 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.

Unusable stack trace after retracing

This is an alternative to the previous response, if there is a good chance that another retrace will work better (e. g. outdated package versions). Please close the bug as invalid with this comment:

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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

If you are sure the reported bug is not caused by the packaging for Ubuntu, it should usually be sent upstream by someone affected by the bug. If appropriate, replace GNOME with the organization behind the software (see https://wiki.ubuntu.com/Bugs/Upstream/ for available organizations):

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

If you have already pointed out that the reported bug is an upstream one, but there hasn't been any feedback about the requested upstream bug for 2 weeks, the reporter (or someone else affected by the bug) might have forgotten it. If that's the case, you should ask if someone has already forwarded the bug upstream and can tell you the number of the upstream bug:

Is there any news about this bug? Has someone affected by this bug sent the report upstream? Could you tell us the bug number, so we can add a bugwatch that will inform us about its status.? Thanks in advance.

However, if you have already sent the bug upstream, you should leave a comment stating where the upstream bug can be found:

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

Old untouched bugs

Old new bugs that haven't been touched in a quite a while and you are UNable to recreate the bug.

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

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!

If you are interested in learning more about software repositories and Ubuntu the following pages should be informative:

1. http://www.ubuntu.com/project/about-ubuntu/components - information about Ubuntu repositories
2. https://help.ubuntu.com/community/Repositories - information regarding managing repositories

Packages provided by Medibuntu

While not supported by Ubuntu, it might be more helpful to a user if we can point them in the right direction if they are looking for something that's in Medibuntu. A package list can be found here: http://packages.medibuntu.org/ Common Packages people are looking for are: Google Earth, Real Player, and Skype

Here's a simple response for one of those packages (Note PKG is a placeholder):

You can get deb packages compatible with Ubuntu for PKG from Medibuntu:
https://help.ubuntu.com/community/Medibuntu

If you encounter any bugs with Medibuntu, report them here:
https://launchpad.net/medibuntu/+filebug

If you have questions about Medibuntu, you can ask them here:
https://answers.launchpad.net/medibuntu/

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 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 - Oneiric Ocelot.

This is a significant 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.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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 - Oneiric Ocelot.

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 - Oneiric Ocelot. 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 understand 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".

Not reported in English

This response is appropriate when a bug is not reported in English or some error messages are not in English.

We noticed that some of the sentences in this bug report are not in English. If they were translated in English they would be more understandable to triagers. Could you please translate them?

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 better. 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 default applications or preferences

This should only be used for bug reports where the scope of the change is quite large or would affect a lot of users.

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. Translations in Ubuntu are handled by the Ubuntu Translations project, so we are going to move this bug report over to that project.

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/ExamplePackageRequest.

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!

Triage Unsuccessful: Back to New/Incomplete Status

Thanks for taking the time to report his bug and comment on it. However, I've noticed that this bug has been Confirmed although there is not clear indication as to how to recreate this bug [ or version of software affected ]. Subsequently, I'm setting its status to Incomplete until that information is provided. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status. Thanks for taking the time to make Ubuntu better!

Release has reached EOL

If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to Incomplete and use the following response (Note RELEASE and DATE are placeholders):

Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

An idea to improve Ubuntu

  • Note: If it is a request to add a feature to a specific program it should be forwarded to the upstream developers instead. See: Forwarding Bugs Upsteam

Not everybody requesting an improvement should be directed to brainstorm. Only larger things, or instances where it would be good to get the feedback of users, such as changing a default program. If you redirected the reporter to brainstorm, please close the bug as Invalid.

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 http://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!

Patch attachment not flagged as a patch

When reviewing bug attachments you might find an attachment that is a patch, but is not flagged. Let people know what a patch is!

Looking at the attachments in this bug report, I noticed that an attachment was not flagged as a patch. A patch contains changes to an Ubuntu package that will resolve a bug and this attachment is one! Subsequently, I've checked the patch flag for it. In the future when submitting patches please use the patch checkbox as there are some Launchpad searches that use this feature. You can learn more about the patch workflow at https://wiki.ubuntu.com/Bugs/Patches.

Attachment incorrectly flagged as a patch

When reviewing bug attachments you might that someone flagged an attachment that is a patch, but it really isn't one. Educate people know what a patch is!

Looking at the attachments in this bug report, I noticed that one was flagged as a patch incorrectly. A patch contains changes to an Ubuntu package that will resolve a bug, since this was not one I've unchecked the patch flag for it. In the future keep in mind the definition of a patch. You can learn more about what qualifies as a patch at https://wiki.ubuntu.com/Bugs/Patches. Thanks!

Package installation failure

If the problem looks like local file system corruption (e. g. bug 322714, which indicates broken/truncated dpkg .list files), it is most likely not something we can fix in Ubuntu in general. Since we have a large number of such bugs, it is probably best to close it as invalid (or incomplete if you want to followup and subscribe) with this comment:

Thank you for your report. This package failure looks like being caused by a corrupted file system. Please start the "Memory check" from the boot menu. If that runs successfully, please start the desktop cd. Hold right-shift key after the bios checks to get to the grub menu and run "Check disc for errors" option. If the file system corruption is serious, the safest option would be to reinstall your system.

Security Bugs

For a number of situations, we have stock reply scripts that can used from the lp:ubuntu-qa-tools git tree, in the responses/security/ subdirectory.

Not Security

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

Invalid One Hundred Paper Cuts

A Short name could be "Invalid Papercut" / "Invalid ppc"

Thank you for reporting this issue and bringing it to our attention. However, this bug is not a valid paper cut, as a paper cut should be a small usability issue, in the default or featured applications, that affects many users and is quick and easy to fix.
Therefore this bug cannot be addressed as part of the One Hundred Paper Cuts project.

<explanation why bug is not a papercut>
For further info about the paper cut criteria, please read <https://wiki.ubuntu.com/PaperCut>.

Don't worry though, This bug has been marked as "Invalid" ONLY in the One Hundred Paper Cuts project.

Added Bugwatch

Thanks for taking the time to report this bug in the upstream bug tracking system this is a tremendous help. Launchpad has the ability to watch lots of upstream bug trackers and this can be done by following the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've added the bug watch for this bug report.

Other projects have standard responses as well:


Back to HelpingWithBugs.

CategoryBugSquad

Other languages

Bugs/Responses (last edited 2021-07-25 15:18:50 by paulw2u)