DebuggingUbiquity
|
Size: 2686
Comment:
|
Size: 3755
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Crash report handling == | <<Include(Debugging/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>|| |
| Line 3: | Line 4: |
| Many Ubiquity bugs arrive in the form of cut-and-pastes from its crash helper dialog. In simple cases, these are often enough to completely diagnose the bug and allow a developer to fix it, which is why the crash dialog exists. However, if the crash occurs in `install.py` (the component of Ubiquity that actually constructs and configures the newly-installed system), then in Dapper a combination of technical awkwardness and lack of developer time (which should be resolved for Edgy) means that the traceback from the crash dialog often ends like this: | = Crash report handling = Many Ubiquity bugs arrive in the form of cut-and-pastes from its crash helper dialog. In simple cases, these are often enough to completely diagnose the bug and allow a developer to fix it, which is why the crash dialog exists. However, if the crash occurs in `install.py` (the component of Ubiquity that actually constructs and configures the newly-installed system), then in Dapper a combination of technical awkwardness and lack of developer time means that the traceback from the crash dialog often ends like this: |
| Line 9: | Line 12: |
| This traceback is moderately useless on its own, and you must not mark bugs as duplicates on the basis that they both contain a traceback such as this. The real error is hidden in /var/log/installer/syslog, so if the reporter didn't attach that, ask for it, and for /var/log/syslog and /var/log/partman as well for good measure. Look for the traceback from the crash dialog in /var/log/installer/syslog and then trace up a little bit; the real error should be there, often in the form of a subprocess exiting non-zero. | (Edgy installations will produce a more verbose traceback.) |
| Line 11: | Line 14: |
| == Specific known issues in Dapper == | This traceback is moderately useless on its own, and you must not mark bugs as duplicates on the basis that they both contain a traceback such as this. In Dapper, the real error is hidden in /var/log/installer/syslog, so if the reporter didn't attach that, ask for it, and for /var/log/syslog and /var/log/partman as well for good measure. Look for the traceback from the crash dialog in /var/log/installer/syslog and then trace up a little bit; the real error should be there, often in the form of a subprocess exiting non-zero. |
| Line 13: | Line 16: |
| * Crash if /boot is on XFS: [https://launchpad.net/bugs/47848 #47848] This can be recognised by grub-installer exiting 10 or 30, and /var/log/partman or /var/log/installer/syslog (look for "mountpoints:" in the latter) indicating that / is on XFS and there is no non-XFS /boot filesystem. Feel free to mark such bugs as duplicates of #47848, with text such as: {{{ Thanks for your report. You need to use a non-XFS root filesystem or create a non-XFS /boot filesystem. Bug 47848 is filed to note that the partitioner should warn you about this up-front. |
Standard text for asking for log files in Dapper: {{{ Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance. |
| Line 19: | Line 20: |
| * Crash if system partitions are not reformatted: [https://launchpad.net/bugs/47046 #47046] | Standard text for asking for log files in >= Edgy: {{{ Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance. }}} |
| Line 21: | Line 24: |
| This can be recognised by an OS``Error exception being thrown from the `copy_all` function, usually "File exists" or similar, and a "mountpoints:" line in /var/log/installer/syslog that includes a tuple with a standard filesystem (e.g. /, /boot, /usr, or /var; not /home or /media/*) as the first item and False as the second item. Feel free to mark such bugs as duplicates of #47046, with text such as: {{{ Thanks for your report. At present, you must reformat system partitions (e.g. /, /boot, /usr, or /var) during installation; bug 47046 is filed to note that the partitioner should warn you about this up-front. If you are upgrading an existing installation, then please see http://wiki.ubuntu.com/DapperUpgrades rather than using this installer. }}} |
Don't ask for `/var/log/installer/syslog` if the version of ubiquity in the log is `1.1.12` or greater (Edgy or later). Those versions of ubiquity send all log messages apart from certain detailed partitioning log messages to `/var/log/syslog`, and `/var/log/installer/syslog` no longer exists. Please do not assign ubiquity bugs to anyone unless you're a ubiquity developer or you manage a ubiquity developer. Please don't reject ubiquity bugs unless you're a ubiquity developer. In general, please try to refrain from causing unnecessary extra bug mail noise for ubiquity developers or from taking items off their to-do lists without consulting them first. = Known bugs = Before filing new bugs, check that it is not already [[https://bugs.launchpad.net/ubuntu/+source/ubiquity|listed in Launchpad]] = Non-bugs = Certain hardware failures can often be reported as installer bugs. This includes faulty CDs, CD drives hard drives and memory. = Notes = The 'kernel command line' line of the syslog file contains information about the boot parameters used. * Images created by unetbootin contain 'initrd=/ubninit' and / or 'BOOT_IMAGE=/ubnkern' Bugs should be tagged indicating the step where the issue occurred if possible. The possible steps are: * ubi-console-setup * ubi-language * ubi-migrationassistant * ubi-network * ubi-partman * ubi-prepare * ubi-tasks * ubi-timezone * ubi-usersetp - "Who are you?" * ubi-webcam * ubi-wireless ------ '''Also see:''' * DebuggingUbiquity/AttachingLogs * DapperReleaseNotes/UbiquityKnownIssues * DebuggingUbiquity/DupCandidates ---- CategoryBugSquad CategoryDebugging |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Contents |
Crash report handling
Many Ubiquity bugs arrive in the form of cut-and-pastes from its crash helper dialog. In simple cases, these are often enough to completely diagnose the bug and allow a developer to fix it, which is why the crash dialog exists. However, if the crash occurs in install.py (the component of Ubiquity that actually constructs and configures the newly-installed system), then in Dapper a combination of technical awkwardness and lack of developer time means that the traceback from the crash dialog often ends like this:
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog
(Edgy installations will produce a more verbose traceback.)
This traceback is moderately useless on its own, and you must not mark bugs as duplicates on the basis that they both contain a traceback such as this. In Dapper, the real error is hidden in /var/log/installer/syslog, so if the reporter didn't attach that, ask for it, and for /var/log/syslog and /var/log/partman as well for good measure. Look for the traceback from the crash dialog in /var/log/installer/syslog and then trace up a little bit; the real error should be there, often in the form of a subprocess exiting non-zero.
Standard text for asking for log files in Dapper:
Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.
Standard text for asking for log files in >= Edgy:
Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.
Don't ask for /var/log/installer/syslog if the version of ubiquity in the log is 1.1.12 or greater (Edgy or later). Those versions of ubiquity send all log messages apart from certain detailed partitioning log messages to /var/log/syslog, and /var/log/installer/syslog no longer exists.
Please do not assign ubiquity bugs to anyone unless you're a ubiquity developer or you manage a ubiquity developer. Please don't reject ubiquity bugs unless you're a ubiquity developer. In general, please try to refrain from causing unnecessary extra bug mail noise for ubiquity developers or from taking items off their to-do lists without consulting them first.
Known bugs
Before filing new bugs, check that it is not already listed in Launchpad
Non-bugs
Certain hardware failures can often be reported as installer bugs. This includes faulty CDs, CD drives hard drives and memory.
Notes
The 'kernel command line' line of the syslog file contains information about the boot parameters used.
- Images created by unetbootin contain 'initrd=/ubninit' and / or 'BOOT_IMAGE=/ubnkern'
Bugs should be tagged indicating the step where the issue occurred if possible. The possible steps are:
- ubi-console-setup
- ubi-language
- ubi-migrationassistant
- ubi-network
- ubi-partman
- ubi-prepare
- ubi-tasks
- ubi-timezone
- ubi-usersetp - "Who are you?"
- ubi-webcam
- ubi-wireless
Also see: