[Ubuntu Wiki] Update of "Bugs/Responses" by penalvch
Ubuntu Wiki
noreply at ubuntu.com
Mon Nov 16 11:27:00 UTC 2015
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/Responses" page has been changed by penalvch:
http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=375&rev2=376
Comment:
1) Due to LP#1516213 et. al. added only once for requests to apport-collect. 2) RM'ed EOL mentioning. 3) RM'ed usplash as not supported. 4) Presentation fixes.
<<TableOfContents>>
= Not described well =
- ||<tablestyle="background-color: #eee">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.<<BR>><<BR>> We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures <<BR>><<BR>>At a minimum, we need:<<BR>>1. the specific steps or actions you took that caused you to encounter the problem,<<BR>>2. the behavior you expected, and<<BR>>3. the behavior you actually encountered (in as much detail as possible).<<BR>>Thanks! ||
+ ||<tablestyle="background-color: #eee">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.<<BR>><<BR>> We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. <<BR>><<BR>>At a minimum, we need:<<BR>>1. The specific steps or actions you took that caused you to encounter the problem.<<BR>>2. The behavior you expected. <<BR>>3. The behavior you actually encountered (in as much detail as possible).<<BR>>Thanks! ||
= Missing Steps to Recreate Bug =
- ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:<<BR>><<BR>>* Is this reproducible?<<BR>>* If so, what specific steps should we take to recreate this bug?<<BR>><<BR>>This will help us to find and resolve the problem.||
+ ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:<<BR>>* Is this reproducible?<<BR>>* If so, what specific steps should we take to recreate this bug?<<BR>><<BR>>This will help us to find and resolve the problem.||
= Missing Apport Information =
- ||<tablestyle="background-color: #eee">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:<<BR>>apport-collect BUGNUMBER<<BR>>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.||
+ ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:<<BR>>apport-collect BUGNUMBER<<BR>><<BR>>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:
@@ -30, +30 @@
== Debugging Kernel General ==
Pleas also see the Ubuntu Kernel Teams [[https://wiki.ubuntu.com/Kernel/BugTriage/Responses|specific responses]] for linux (Ubuntu) kernel bugs.
-
== Debugging Sound Problems ==
- ||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.<<BR>><<BR>>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.||
+ ||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.<<BR>><<BR>>This information can be gathered for you automatically by using the following command only once:<<BR>>apport-collect -p alsa-base BUGNUMBER<<BR>><<BR>> where BUGNUMBER is the number of the bug you've reported.||
-
== Debugging ACPI ==
||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.||
-
== Debugging Removable Devices ==
||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested at https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.||
-
== Debugging Printing problems ==
||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested at https://wiki.ubuntu.com/DebuggingPrintingProblems as separate attachments.||
-
== Debugging Hardware Detection ==
||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.||
-
== Debugging USB Storage ==
||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>Please include the information requested at https://help.ubuntu.com/community/DebuggingUSBStorage as separate attachments.||
-
== Debugging Xorg in general ==
+ ||<tablestyle="background-color: #eee">Thank you for taking the time to report this bug and helping to make Ubuntu better. In order to attach necessary information for debugging this as an Xorg problem please run the following command only once:<<BR>>apport-collect BUGNUMBER<<BR>><<BR>>Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thanks in advance.||
- ||<tablestyle="background-color: #eee">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. Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thanks in advance.||
-
== Freeze during boot or shutdown screen ==
- ||<tablestyle="background-color: #eee">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:<<BR>><<BR>>1. Hold Esc during Grub boot delay to access the boot menu. <<BR>>2. Select your actual Ubuntu boot line and press "e" to edit it. <<BR>>3. Select the "kernel" line and press "e" to edit it. <<BR>>4. At the end of the line, remove "splash" and "quiet" and press "enter". <<BR>>5. Type "b" to boot the custom boot line.||
-
- For Lucid and subsequents releases users :
||<tablestyle="background-color: #eee">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:<<BR>><<BR>>1. Hold Right-Shift during Grub boot delay to access the boot menu. <<BR>>2. Select your actual Ubuntu boot line and press "e" to edit it. <<BR>>3. Select the "linux" line and at the end of the line, remove "splash" and "quiet". <<BR>>5. Type "F10" to boot the custom boot line.||
== Debugging Plymouth ==
- ||<tablestyle="background-color: #eee"> 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 a plymouth problem. Thanks in advance.||
+ ||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Please run the following command only once via a terminal:<<BR>>apport-collect BUGNUMBER<<BR>><<BR>> which will attach necessary information for debugging this as a plymouth problem. Thanks in advance.||
== Debugging Live Installation ==
||<tablestyle="background-color: #eee">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.<<BR>><<BR>>Please execute the following command 'ubuntu-bug ubiquity' as it will gather detailed information regarding your installation. Thanks in advance.||
@@ -76, +65 @@
||<tablestyle="background-color: #eee">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 ==
- ||<tablestyle="background-color: #eee">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.||
+ ||<tablestyle="background-color: #eee">Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please run the following command only once in a terminal:<<BR>>apport-collect BUGNUMBER<<BR>><<BR>>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.
@@ -100, +89 @@
Please see the [[https://wiki.ubuntu.com/DebuggingOpenldap|debugging openldap]] article for debugging and stock replies.
== Debugging ffmpeg (mostly libavcodec and libavformat bugs) ==
- ||<tablestyle="background-color: #eee">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:<<BR>><<BR>>1. Reproduce it;<<BR>>2. Check if it happens with the latest version; and<<BR>>3. Understand where it actually crashes.<<BR>><<BR>>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.<<BR>><<BR>>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)||
+ ||<tablestyle="background-color: #eee">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:<<BR>><<BR>>1. Reproduce it;<<BR>>2. Check if it happens with the latest version; and<<BR>>3. Understand where it actually crashes.<<BR>><<BR>>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.<<BR>><<BR>>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).||
== Debugging SCIM related issues ==
+ ||<tablestyle="background-color: #eee">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.<<BR>><<BR>>Please post or attach the following:<<BR>> 1. the output of 'dpkg -l | grep scim'<<BR>>2. the output of 'im-switch -l'<<BR>>3. the files '/etc/scim/config', '/etc/scim/global' and '~/.scim/config'<<BR>><<BR>>Additionally, please answer the following questions:<<BR>>1. Is this bug reproducible (always/sometimes/no)?<<BR>>2. If you can reproduce the bug, what are the steps to do so?<<BR>>3. Which desktop environment are you using? (Gnome/KDE3/KDE4)<<BR>>4. If you remove '~/.scim/config', '~/.scim/global' and restart your X session by logging out and in again, does this bug still appear?<<BR>>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?||
- {{{
- 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 =
Some bugs are never responded to by the submitter (also called "original poster", or "OP"). These bugs will be automatically expired by Launchpad in 60 days, counted from the day it was set incomplete. There is no need to act on them (and, actually, changing the bug will restart the expiry period).
@@ -128, +103 @@
/!\ 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.
- ||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>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.||
+ ||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>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.
@@ -140, +115 @@
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.
- ||<tablestyle="background-color: #eee"> 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 ISO of the development release - Vivid Vervet. 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.||
+ ||<tablestyle="background-color: #eee"> 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 ISO of the development release - Vivid Vervet. 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 =
||<tablestyle="background-color: #eee"> 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.<<BR>><<BR>>If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.<<BR>><<BR>>Now open your file manager, navigate to your {{{/var/crash}}} directory and open the crash report you wish to submit.<<BR>>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'}}}.<<BR>><<BR>>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.
@@ -179, +153 @@
||<tablestyle="background-color: #eee"> 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.
+ Old new bugs that haven't been touched in a quite a while and you are unable to recreate the bug.
- ||<tablestyle="background-color: #eee"> 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. ||
+ ||<tablestyle="background-color: #eee"> 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 only once:<<BR>>apport-collect <bug #><<BR>><<BR>> and any other logs that are relevant for this particular issue. ||
## Also we are actively promoting testing the development release of Ubuntu so something like this could be added:
## ||<tablestyle="background-color: #eee"> The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Vivid Vervet. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ ||
-
= 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'''.
- ||<tablestyle="background-color: #eee">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! <<BR>><<BR>>If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories||
+ ||<tablestyle="background-color: #eee">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! <<BR>><<BR>>If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/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#Procedure|Stable Release Update (SRU)]]:
@@ -200, +173 @@
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:
- ||<tablestyle="background-color: #eee"> 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 - Vivid Vervet.<<BR>><<BR>> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport ||
+ ||<tablestyle="background-color: #eee"> 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 - Vivid Vervet.<<BR>><<BR>> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport.||
The bug's state should become '''Fix Released''' and if the package can not be backported:
||<tablestyle="background-color: #eee"> 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 - Vivid Vervet. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://wiki.ubuntu.com/UbuntuBackports for more information. ||
= Reported by someone not respecting the Code of Conduct =
- ||<tablestyle="background-color: #eee"> Thank you for your bug report. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. ||
+ ||<tablestyle="background-color: #eee"> Thank you for your bug report. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. ||
##== A non-trivial feature request ==
## Commenting out per cjwatson need a good idea for a replacement though
@@ -241, +214 @@
= About an incorrect translation =
||<tablestyle="background-color: #eee"> Thank you for taking the time to report this bug and helping to make Ubuntu better. Translations in Ubuntu are handled by the [[https://launchpad.net/ubuntu-translations|Ubuntu Translations]] project, so we are going to move this bug report over to that project. ||
-
-
= Incomplete Package Request =
||<tablestyle="background-color: #eee">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.||
@@ -255, +226 @@
= Release has reached End of Life (EOL) =
If the specific release has reached End of Life 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>>See this document for currently supported Ubuntu releases: 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 upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.<<BR>><<BR>>Do feel free to report any other bugs you may find.||
+ ||<tablestyle="background-color: #eee">Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<<BR>>See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases <<BR>><<BR>>I've tried recreating this bug with your release and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.<<BR>><<BR>>Do feel free to report any other bugs you may find.||
= Patch attachment not flagged as a patch =
When reviewing bug attachments you might find an attachment that is a [[ Bugs/Patches | patch ]], but is not flagged. Let people know what a patch is!
More information about the Ubuntu-bugsquad
mailing list