20080226

Contents

    1. 150 bugs with status "New" about ubiquity
  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 Plymouth
    11. Debugging Live Installation
    12. Debugging A Distribution Upgrade
    13. Debugging GNOME Power Manager
    14. Debugging Network Manager
    15. Debugging Firefox
      1. Firefox crash report that fails retrace
    16. Debugging Samba
    17. Debugging Openldap
    18. Debugging ffmpeg (mostly libavcodec and libavformat bugs)
    19. 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
  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 End of Life (EOL)
  29. Patch attachment not flagged as a patch
  30. Attachment incorrectly flagged as a patch
  31. Package installation failure
  32. Security Bugs
  33. Added Bugwatch
  34. Hanging Application or Daemon
  35. User Incorrectly Subscribing a team to a Bug
  36. Links
    1. 50 bugs with an "Incomplete" status
    2. Progress

Here we have a sampling of bugs to work on for Hug Day. After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding lightgreen in the first cell of the column after "background-color:" and before ";". This will let people know that the bug in that row has been hugged.

You might find it more convenient to edit the wiki page using editmoin a command line utility for editing moinmoin wiki pages. It is available as a package in Gutsy and Hardy. More information including an easier way to do this was mailed to the Bug Squad.

150 bugs with status "New" about ubiquity

These bugs have not yet been triaged. Detailed information about debugging ubiquity can be found at the DebuggingUbiquity page. A reply you might want to use is

Include: Nothing found for "=== Debugging Live CD Installation ==="!

Include: Nothing found for "== Incomplete bugs without a response from submitter =="!

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

These standard responses along 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-bugcontrol-tools in the file gm-xml-files/bugsquad-replies.xml. To check out a branch, use

bzr branch lp:ubuntu-bugcontrol-tools

Only members of bug-control can commit to this branch. But you can submit a merge proposal, Brian Murray will review/merge it (see this email message), and they can be used when replying to a bug report if merged.

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 Plymouth
    11. Debugging Live Installation
    12. Debugging A Distribution Upgrade
    13. Debugging GNOME Power Manager
    14. Debugging Network Manager
    15. Debugging Firefox
      1. Firefox crash report that fails retrace
    16. Debugging Samba
    17. Debugging Openldap
    18. Debugging ffmpeg (mostly libavcodec and libavformat bugs)
    19. 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
  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 End of Life (EOL)
  29. Patch attachment not flagged as a patch
  30. Attachment incorrectly flagged as a patch
  31. Package installation failure
  32. Security Bugs
  33. Added Bugwatch
  34. Hanging Application or Daemon
  35. User Incorrectly Subscribing a team to a Bug
  36. Links

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

Pleas also see the Ubuntu Kernel Teams specific responses for linux (Ubuntu) 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. 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

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 Lucid 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 "F10" to boot the custom boot line.

Debugging Plymouth

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.

Debugging Live 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 execute the following command 'ubuntu-bug ubiquity' as it will gather detailed information regarding your installation. 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

Please see the debugging Samba article for debugging and stock replies.

Debugging Openldap

Please see the debugging openldap article for debugging and stock replies.

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

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). Note that this applies for the Ubuntu project (i.e., those bug tasks that have "(Ubuntu)" in their name). Other projects may, or may not, have automatic incomplete bug expiration set.

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 ISO, 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 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

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, 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 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 - Vivid Vervet.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible 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 - Vivid Vervet.

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:

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

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 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 is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at http://askubuntu.com or http://ubuntuforums.org. 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.

Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to 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 ISO.

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 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 this 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 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):

Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.
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 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.

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 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 ISO. 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

Please see the Ubuntu Security Team's bug triage page.

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.

Hanging Application or Daemon

Thanks for your interest in helping to resolve this issue. In order to get to the bottom of this we need to figure out where the program is hanging. If you can follow the steps on https://wiki.ubuntu.com/Backtrace#Already_running_programs and attach the generated text file to this bug it would be of great help.

User Incorrectly Subscribing a team to a Bug

Thanks for your interest in helping to resolve this issue. There is no need to subscribe anyone to this bug, as it generates unnecessary emails and will not resolve the issue any faster. Your bug will be looked at by a developer as time permits.

Links

Other projects have standard responses as well:


Back to HelpingWithBugs.

CategoryBugSquad

To mark it off the list you should:

  • Ask the reporter for more detailed information, subscribe yourself to the bug and mark it "Incomplete" or

  • Set it "Confirmed" and set an importance (if you are not a QA member ask someone for help)

Bug

Subject

Triager

194287

crashed trying to install mythbuntu

superm1

194260

installer hangs after keyboard selection

Iulian

194229

the installer crashed. The LiveCD don't eject.

cjwatson

194152

Installer crashed

superm1

194130

installer crashed cause: timezone

cjwatson

194026

[Hardy] ubiquity hangs at hardware setup

193552

Support 256MB machines in Ubiquity.

evand

193540

Cannot resize ntfs partitions in Ubiquity.

193270

"Failed to unmount partitions" dialog unintuitive

193267

Should not install to /dev/fd* or /dev/ccache

192685

Installer should have a "reboot when done" checkbox

cjwatson

192611

Cannot manually partition a new hard disk in installer

191424

xubuntu 64 not on grub bootlist

191383

Hardy Alpha amd64 alternate installer did not recognize Attansic Ethernet controller

BrianMurray

191119

Installer corrupts raid drive

191112

Installer Manual option confusing to use

MichaelLosonsky

191109

Installer uses inconsistent drive names

190598

Ubiquity freezes at 100% (Copying Installation Logs)

MichaelLosonsky

190596

HDD not bootable if ubiquity fails

190494

Ubiquity attempts resize on mounted partition

190203

Install Ubuntu without GRUB.

Andrewsomething

190094

Third Installer Crash - Kubuntu 6.06.1

190040

When using manual partitioning "Mount point" dropdown box is empty in Hardy Alpha4

BrianMurray

190036

Illogical response to "New partition table" in alpha4

evand

189824

Install crashed on Kubuntu 6.06.1

189754

Ubuntu is in English, but should to be in Spanish

cjwatson

189323

(Hardy Alpha 4) kubuntu installer exits without feedback upon completion

BrianMurray

189281

Gutsy Gibbon partition manager

189193

Installer crashed

188759

install user doesn't belong to all "administrative" groups

188706

Kubunto Installation on Usb-HD failed

188503

Hardy Alpha 4 Wipes Out Other Partitons

188289

Installer crashes when creating or formatting partitions

188282

hardy install alpha4 loops: broadcom: no firmware file

BrianMurray

188120

[Hardy] Install from 20080131.2 LiveCD deleted data from all Windows partitions

MichaelLosonsky

188011

formats hard disk when not requested to

187973

installation crashed while formating the hard disk

187437

Installer missing graphics

187163

Message in GUI installer talks about apt and sources.list

BrianMurray

186959

Unmatched passwords message appears and disappears unnecessarily late

186953

"Cancel" button is inconsistently placed

186951

"Back" and "Forward" aren't as obvious as they could be

186895

partition not working in grub

186256

[Ubuntu 8.04 Hardy i386 desktop alpha-3+ daily-build] Guided entire disk installation fails when installing onto existing Ubuntu system that should be over-written.

BrianMurray

186224

installer crashed

185348

Can't create root ("/") partition on a disk

184838

Unable to toggle "Format?" flag with keyboard at the install wizard's manual partitioning page

184538

Ubiquity freezes when cancelling a manual partition change

184185

unable to install with Danish language

184052

[Gutsy]: Ubiquity crashes when installing Dapper in Virtualbox from live cd.

183426

[hardy] alpha-3: i386 desktop cd - partition gui hangs

MichaelLosonsky

182428

hardy installer->maual partition dialog text cut off

Andrewsomething

182098

ubiquity confirm to quite screen can jump behind the main window

181812

Execution of grub-install (hd0) failed)

181525

On GPT disk label, grub-install fails with Fatal error. Stage1 not read correctly.

181418

perl: warning: Setting locale failed.

180622

install aborted with alleged disk error

180089

fatal error on grub-install (hd0) related to partition type

179686

Installation Crash

179269

installer crashed

178984

install procedure crashed on grub-install

178641

Dell m1330 mbr needs overwriting

178608

LiveCD fails on Aspire 1360 with black screen

178372

The Installer Crashed

178299

Can't create new partitions

178183

Ubuntu 7.1 Crashed during installation

177769

Installer crashed

177758

installer crashed during installing system

MichaelLosonsky

177623

autopartitioning doesn't work in localized ubiquity

177597

7.10 installer crashed trying TimezoneApply

177471

"Installer crashed" during installation at about 74%

177096

cd not recognized during installation process

176883

Error while creating new partition

176824

installer crashed

176500

Installer crashed

176341

ambiguity on disk repartitioning

175920

[hardy] ubiquity crashed with InstallStepError in configure_locales()

BrianMurray

173950

Keyboard layout choice in installer confusing

173888

Window maximizing bug

172439

installer gets time wrong

164826

add uninstall linux option

164648

Allow user to select preferred locale

163541

The "guided" installation option computes new size wrongly when it's going to shrink a NTFS partition

161861

Gutsy installer creates a faulty menu.lst when a /boot/ partition is used

161123

gnewsense installation crashed with exit code -11

160154

[gutsy] Installer forces user creation

158964

SATA HDD existing windows/linux partiton not recognised by installer

157459

translations in installer are not always translated

157019

use consistent, recognisable disk names

156296

Installer doesn't offer import of user even if home partition is left untouched

156006

[Gutsy Final] Crash after clicking "Restart Now"

BrianMurray

155928

Installer crashed during installation of Gutsy

155559

If LiveCD user already set time zone, don't ask again

155528

Gutsy install failure (from live CD install)

MiguelRuiz

155308

[enhancement] Password strength meter in user creation

Andrewsomething

155028

[Gutsy] Ubiquity don't finish install

pedro

153933

Gutsy Gibbon install: grub failes with /dev/hda4

152012

ubiquity messes with sound volume

151973

installer selects disk that's too small by default

151630

Allow passwordless installs?

149911

[Installer] progress window is too small to fit text

148840

grub install fails on (hd0)

148499

resized NTFS partition is not detected

146729

[gutsy] download language support can't be ignored

146685

Bug when typing keyboard layout name too fast

146175

Resizing partition without dialogue

145516

Ubuntu installer can't create large ReiserFS partitions

145136

Installer Crashed report when installing grub

144414

Localization issues and more.

141441

[apport] ma-search-users crashed with SIGSEGV

141430

Other OSes added to GRUB menu even when GRUB installed to partition (not MBR)

140505

complicated ubiquity migration + user import

Andrewsomething

139359

Gutsy Tamil Installation - Problem

138422

ubiquity does not allow xfs on /boot

138096

kubuntu feisty installer fails on previously partitioned disk

137343

feisty life cd does not create bootrecord

MiguelRuiz

135900

problem in migration-assistant on ubuntu gutsy tribe 5

135732

ubuntu installer deletes partitions?!

135688

Installer: insufficient privileges to set the clock when clock not set.

135370

[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs

134710

Installer hangs indefinitely if it's told to mount Vista partition

132934

crashed in live CD Kubuntu 64 install manual layout

132181

Ubiquity failed to fetch openoffice.org language packs

131274

[Tribe4] can't install. DD mounted during installation

131084

Partitioning language needs resimplification

131056

problem with manual partitioning and changing size of partition

130463

Installer does not inform user that it can setup a dual boot system with operating systems like Windows

130045

ubiquity installer on gutsy testing 3 hangs on prompts

129810

[dapper] Installer crashed

128955

installer has crashed twice from Live CD

127946

upon installation the GRUB menu.lst file is generated wrong

127871

Installer crashes when clicking on skip when downloading languages pack

127678

ubiquity crashes when configuring boot loader

pedro

127626

creat id by import from xp can't login

127411

Installer crashed at 93% (6.06.1)

127061

cannot select mount point when creating partition

125671

Duplicate edit partition dialog hang the installer

Iulian

125246

Progress bar not showing in Ubuntu Feisty

Iulian

124771

[feisty 32 & 64 live-cd install] manual parted rescans disk with every change, taking several minutes

124372

Install -> prepare disk space -> hung when using the new partition slider

124033

Gutsy: Keyboard was not set correctly after install.

123732

Feisty Desktop CD installation Hangs at 5% on AMD64 with SATA

123301

ubiquity crashed with DebconfError in command()

121214

Gutsy(beta) install did not recognise other Linux distros on disk, ie they do not appear in GRUB

121150

Wrong locale setting when choose Hong Kong as the location

119584

Installing Ubuntu removes both UUID and LABEL from partition

119520

Locked out from Kubuntu install

119026

Installer crashed

Iulian

118442

[apport] ubiquity crashed with KeyError in get_autopartition_choice()

117803

Installation stuck at Migration step

117676

no options of "FORWARD"/"BACK"/"CANCEL" throughout the installation process.

Iulian

117605

installer crashes when installing packages

50 bugs with an "Incomplete" status

These bugs have had some initial triage done and may or may not have had a response from the original reporter. We can either set the status to "Confirmed" or if there is absolutely not enough information for anyone to recreate the bug then it should be set to a status of "Invalid".

To mark it off the list you should:

  • Set the status to "Confirmed" if the reporter has provided the requested information or

  • Set the status to "Invalid" if the reporter had not responsed and there is no way anyone could work on the bug or

  • Set the status to "Confirmed" and the prioirty to "Low" if the reporter has not responsed and there may be enough information for someone to work on it

Bug

Subject

Triager

193329

[hardy] [alpha4] bubiquity hangs after language selection, until languagechooser is -KILL'ed

Iulian

192817

crash during install, when choosing partition, tried to resize with slider bar and freezes

Iulian

187586

mythbuntu 7.10 installer crash

Iulian

186094

installer crashed at Configuring Additional Service

superm1

183731

Installation Gutsy (7.10) with kde4 failed.

178675

Install in 7.10 stalls after input of all preferences, fails to advance install any further

Iulian

178305

graphical time-zone doesn't progress to next screen

Iulian

178258

live cd hardy alpha2 crashes during instal procedurel

Iulian

177641

installer crashed

Iulian

165320

cannot format ext3 partition on laptop during installation

MichaelLosonsky

163719

Installer Crashed at 78%

160900

partition ignorance

Iulian

156438

Ubiquity does not allow using an existing partition as '/'

155608

Choosing smallest possible partition size for resizing a NTFS partition during installation breaks MBR and install

Iulian

150766

Usability issue during install when setting nonexistent mount point

Iulian

149206

Install stays busy after clicking "Forward" on "Migrate documents and settings"

145727

[installer] trys to unmount /migrationassitant (never mounted)

Iulian

140069

ubiquity partition editor crahes when trying to edit a partition some partition types defined incorrectly

Iulian

138326

X8ubuntu install on usb pen drive (8GB) crashes

Iulian

137069

Installation failure over Freespire

Iulian

134933

Installer Crashed

Iulian

134912

Installer crashed - GrubInstaller failer

Iulian

134719

ubiquity eat 100% CPU in Kubuntu 7.10 Tribe 5

Iulian

133439

multiple ubuntu boots 7.10 installation

133102

installer crashed

Iulian

133058

install failed with exit code 139

Iulian

131859

installer crashed

Iulian

131630

fglrx not installed

131347

Tribe 4 installer creates unbootable system

Iulian

130303

yaboot failed to load on install

Iulian

128295

Trying to install

Iulian

126992

Installer crash on a virtual machine (MS Virtual PC2007)

Iulian

123334

"ubiquity" crashed during Ubuntu installation - account and password creation

121132

partition detection crashed during installation

Iulian

121124

Installing new version (Gutsy) next to old reformats swap; makes swap fail on boot in other OSs

120123

[Tribe1] Manual partitioning gives inconsistent units

110904

Auto mount crashes installer

107714

installing on a usb thumb drive error, timezone apply error

Iulian

107234

Installer crashes in partitioning

MichaelLosonsky

106643

[m-a] Feisty installation stops at 88%

Iulian

106344

Kubuntu Feisty beta installer crashes during startup of ubiquity partitioner

Iulian

105170

confusing dailog window after partitioning at install

Iulian

105104

[Feisty] Crash when preparing to install with busy mounted partitions

103629

[apport] ubiquity crashed with AttributeError in on_next_clicked()

102482

Endless "Too small size" error popup

Iulian

99908

The ext3 file system creation in partition #1 of SCSI1 (0,0,0) (sda) failed.

97160

Empty dialogboxes

Iulian

97081

Installer hangs at step 5

96053

can't install kubuntu 7.04 beta

Iulian

95467

installer crashes after warning about mounted partitions

Iulian

94970

Crash when getting to the "partition disk" screen.

Progress

The graphs are static as the Hug Day is over.

ubiquity-1day-new.png ubiquity-1day-incomplete.png ubiquity-1day-confirmed.png


CategoryBugSquad

UbuntuBugDay/20080226 (last edited 2008-08-06 17:00:54 by localhost)