20080325

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. 41 bugs with an "Incomplete" status
    2. Progress

Today's Bug Day will focus on ubiquity - the Live CD installer. Since Hardy Beta was recently released, we felt it would be a good idea to focus on ubiquity bugs to help ensure everyone has a pleasant experience installing Ubuntu.

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.
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 only once, 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.

This information can be gathered for you automatically by using the following command only once:
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. In order to attach necessary information for debugging this as an Xorg problem please run the following command only once:
apport-collect BUGNUMBER

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 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 following command only once via a terminal:
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 the following command only once in a terminal:
apport-collect BUGNUMBER

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. 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. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

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 only once:
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.

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.

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. 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 https://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 (just delete the lines that are not relevant):

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

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

206085

[Hardy beta] installer doesn't migrate settings

205762

hardy install ubiquity freezes during partitioning stage

Andrewsomething

205117

Graphic for Manual Partition wrong size Kubuntu KDE4 8.04 Beta Desktop

heno

204245

[Hardy alpha6] LiveCD install progress disappears after 86ish% done

sbarjola

204187

No compressed file system option in ubiquity.

Andrewsomething

204024

installer crashed

Andrewsomething

204007

incomplete string in disk resize dialog in installer

203977

Install applications chooser

203931

kubuntu oem-config allows you to "continue using Live CD"

203909

Network Proxy settings in Advanced dialog lack translations/i18n

Andrewsomething

203907

Hardy's migrate tool lacks translations/i18n

Andrewsomething

203660

Partition formatting message unclear

203626

Kubuntu installer: Edit partition dialog rendering error

203622

Kubuntu installer: does not keep track of selected disk options

203423

Timezone map zooming is too sudden and disorienting

203307

ubiquity-frontend-kde does not have the oxygen style

201397

Mythbuntu Control Center MythWeb Password Blanks Out

199433

Kubuntu 8.04-alpha1 installer crashes in partitioner stage

Andrewsomething

199046

ubiquity doesn't have startup notification

198792

Impossible to click on Zurich because it's near Vaduz on the map

198019

MD5 check implementation is inefficient

196075

Hanging ntfs-mounts leave system unbootable when install is cancelled

195415

Ubuntu 7.10 stops installing to USB drive

191119

Installer corrupts raid drive

188706

Kubunto Installation on Usb-HD failed

188503

Hardy Alpha 4 Wipes Out Other Partitons

188289

Installer crashes when creating or formatting partitions

188282

[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file

186224

installer crashed

181812

Execution of grub-install (hd0) failed)

178299

Can't create new partitions

178183

Ubuntu 7.1 Crashed during installation

177769

Installer crashed

177597

7.10 installer crashed trying TimezoneApply

176883

Error while creating new partition

155928

Installer crashed during installation of Gutsy

148499

resized NTFS partition is not detected

116406

Instalation chashes

115635

kubuntu Installer Crash on Step 4

115442

Installer crash at almost the end of process.

115406

Ubiquity doesn't handle the case of /boot being on a different partition from /

114841

Installer crashed while loading module sr_mod

114248

Cannot create ext3 partition when installing 7.04 over old HPFS partition

114126

[apport] ubiquity crashed with ValueError in command()

113937

Ubuntu 6.06 Installer crashed

113630

install ubuntu on disk met a install crash ,it said grub failure

113507

installer crash during disk partion

113497

ubiquity does not generate correct menu.lst

112770

Kubuntu Installer Crashed

112516

ubuquity using over 2 GB during apt upgrade due to unused packages

112119

dapper ubqiuty crashed over PPC partitioning

111731

install to an usb disk does not work

110682

6.10 install erased my LVM volumes

110547

Partition Editor Error on Install Feisty

110292

[Kubuntu 7.04] Grubinstaller failed with code 1, SATA

110260

Installation freezes at 83% "language packs"

110184

Installer Crashed on Grub Install

sbarjola

109794

Ubuntu Feisty Fawn PS3 install glitch

109371

Installer crashed

sbarjola

108804

Xubuntu 7.04 installation does not detect existing partitions

108562

Feisty Installer doesn't recognize my existing partitions

108164

7.04 64 bit installer partitioner 3 problems

107908

Can't configure mount point while installing from disk

107793

Created partition has errors after installing

107424

"Installer crashed" by downloading package list by 83%.

106554

Ubuntu's new partition editor in Feisty don't work

106525

attempt to mount a filesystem with type swap failed

105898

langpack download slow, poor progress indication

105748

Xubuntu manual paticion version 20070411 in NTFS

105703

unable to install grub in a partition

105687

Kubuntu 6.10 will not install grub on SATA hard drive, installation ends in fatal error.

104669

installer creshes in grub install

103939

installer crashes while installing to external hd

103583

Improve graphical timezone chooser, provide choice to enter actual timezones

Andrewsomething

103575

Error durring install

99963

Live CD and install, slow and hanging on Toshiba Satellite A15-S129

98827

ubuntu installer crashed

98731

EBADF talking to debconf

97161

feisty installer: time zone mismatch

95994

installer attempts to download package files even without network connectoin

95471

Ubuntu LiveCD Install manual partitioning error msgs

95300

the installer crashed

94640

Old install CDs installs old version of Ubuntu.

94314

herd-5 graphical install -- no matching modes

93969

Install fails with exitcode 1 on 64bit Dapper

92555

install crash

92126

No choice on LILO after the warming when using xfs file system

91801

No clear indication that a reboot is in progress

91793

Language pack setup downloads package lists unnecessarily

91792

Some progress messages are inscrutable

89594

ubuntu 6.06 i386 installer crashed

89225

Dapper 6.06 - Ubiquity 1.0.12 - Installer crashed

88930

Preparing partition step in installer fails

87224

EBADF talking to debconf

86176

uiquity crashes when installing grub (kubuntu feisty herd4)

85796

While installing ubiquity takes 100% CPU time

85413

Bug during install on external drive

84365

Edgy - Installer crashed at 22%, "copying files"

84303

installer crashed

Parthan

83946

Installer Crashed at bootloader configuration

Parthan

83773

Ubuntu Installer crashed

Parthan

82545

Kubuntu installer fails to mark / bootable. System doesn't boot.

82385

live cd installer - should warn when memory low

81783

Grub Installer Crashed

Parthan

81683

language packs are not installed if network is not available during install

81676

partition editor and mount point selector should display the same labels of the "computer" place

80929

Kubuntu 7.04 Herd2 Installer cannot configure keyboard

YuriyKozlov

80690

installer crashed

Parthan

80674

fedora - ubuntu dual boot install crash

80652

After an installer crash (bug 80651), the installer won't start again

78948

New Feisty (Jan 12) can't install

78938

installer crashed

Parthan

78867

Umlauts displayed incorrectly during keyboard layout selection

78759

installer crash on hd2

Parthan

77199

installer crashed

Parthan

77146

install - reading mirror crashes

76614

yaboot installer crashes while installing to iPod via Firewire

75839

My Keyboard can be used in the menu at the start of the live cd rom

75521

Installer crashes @ partitioning step

74605

Unable to update Dapper -> Edgy via Install CD (Feature Request)

74562

Installer Crashed Xubuntu Edgy 2G USB Flash Memory

73715

Edgy installer crashed while "creating user"

72621

Installer for kubuntu edgy (ubiquity and alternate text mode) fails to set language of kdm

72426

Tried to install Kubuntu in another partion. Ubuntu existing in 1, 5. Grub encountered a problem upon boot. System has been broken ever since. Cannot re-install Ubuntu 6.06 or Kubuntu.

72422

Installer Crash

Parthan

71984

InstallStepError: GrubInstaller failed with code 1

Parthan

71956

refuses to let me modify manualy the partition table

70542

kubuntu installer crashed on powerbook g4 PPC

70222

there was some problems at the end of installation process, installer wasn't be able to install grub

70053

Installer crashes

Parthan

69844

Partition setup during install

69696

installer crashed

Parthan

69659

[newbie] grub / boot pbm

69604

Failed install of 6.10 to a multi SATA system

69377

DMRAID 1.0.0.rc13 "no root file system" error. The suggested fix doesn't work.

69271

Ubuntu partitioning procedure (during installation) damages the Acer Recovery Partition with MSWin

69180

Installer does not show partitions

Parthan

69063

Error Trying to install 6.10

Parthan

69035

Installing Edgy with an Italian localization does not install Italian language support

68626

Edgy Desktop LiveCD install erroneously "requires" NewWorld boot partition (and/or Yaboot) on Pegasos

Parthan

68070

Edgy: install to USB drive leaves system unbootable

Parthan

67928

need scroll bar in assigning mount point window

67801

grub installation fails [cdrom open failed]

67669

6.10 Edgy Eft failed installation of yaboot loader on firewire drive installation.

Parthan

67413

Installation partitioner problem

66531

time selector sets hardware clock to UTC even if it defaults to UTC=no later

66282

Macintosh, no such file: /target/sbin/start-stop-daemon.REAL (mv)

66256

Edgy doesn't like KVMs, uses wrong UUIDs and tries to boot from the wrong driv

66213

['/usr/share/grub-installer/grub-installer', '/target'] exited with code 1

65198

crash: rmdir: /var/lib/os-prober/mount: Device or resource busy (ubiquity version 1.0.17)

41 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

192817

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

189824

Install crashed on Kubuntu 6.06.1

183731

Installation Gutsy (7.10) with kde4 failed.

163719

Installer Crashed at 78%

149206

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

Andrewsomething

131630

fglrx not installed

123334

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

Andrewsomething

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

105104

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

103629

[apport] ubiquity crashed with AttributeError in on_next_clicked()

99908

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

97081

Installer hangs at step 5

94970

Crash when getting to the "partition disk" screen.

Andrewsomething

94716

Installer Crashed

94423

[feisty] Swap partition listed as ext2 and swap in fstab

94039

Exception in GTK frontend (herd 5)

93994

complete non response to task

Andrewsomething

93923

Edgy installer doesn't create a proper grub config file

93465

Kubuntu Installer crashed after hanging for a long time while a gnome package installation

93164

wanted to install ubuntu from DVD and the installer crashed

92033

the installer crashed

91962

install crashed w/ 75% files copied: disk full

91239

Partitioning step not newbie friendly

90344

grub error during nubuntu installation

89528

Kubuntu installer crashed while scanning disks (step 5 of 7)

89458

Crashed when trying to put in mountpoint in partitioner

89224

GrubInstaller failed with code 1

Andrewsomething

88582

Ubuntu installation process crashed upon attempted installation of the boot loader

87593

Fiest 7.01 installation disk partition util broke

86926

nstallStepError: GrubInstaller failed with code 1

Andrewsomething

86846

7.04 Feisty Herd4: Can not prepare mount points "/", "/boot", "swap" during the installation with live cd

83161

Ubuntu v6.10 i386 installation crashed

80765

6.10 Installer refuses due to xfs

80683

PC Ubuntu 6.10 installer from live cd crashed on ThinkpadR60

80205

Ubuntu Herd 2 - i386 Desktop CD - Installation Error

78722

Feisty 20070110 -- Grub fails to list old kernel

51587

ubiquity/install.py: Exception in GTK frontend

48778

Installer Crash after partitioning.

40627

wrong keyboard layout after install

38775

Errors with liveCD file system

Andrewsomething

Progress

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


CategoryTemplate

UbuntuBugDay/20080325 (last edited 2008-08-06 17:00:21 by localhost)