AttachingLogs
|
Size: 1578
Comment: create
|
Size: 2055
Comment: explain or replace terminology, move screenshot down, update for 7.04+
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| If you wish to provide a bug report of a crashed installer it is important to also include the relevant log files. These can be found in the Live CD file system while that session is still active. | If you wish to provide a bug report of a crashed installer it is important to also include the relevant log files. These can be found in the Live CD file system just after the crash happened. |
| Line 8: | Line 8: |
| The crash dialog asks you to file a bug at {{{ https://bugs.launchpad.net/distros/ubuntu/+source/ubiquity/+filebug }}} Simply follow the instruction to add a summary and description. Please paste the backtrace displayed by the crash dialog and describe what stage you were at when it crashed, some information about your hardware and any special circumstances. |
The crash report window will pop up. It asks you to file [https://bugs.launchpad.net/ubuntu/+source/ubiquity/+filebug a bug under the ubiquity package]. Follow the instructions to add a summary and description. Please copy and paste the 'traceback' displayed, and describe what stage you were at when it crashed. |
| Line 18: | Line 12: |
| When you have entered the text and saved it you can add further attachments. Click 'Add a comment/attachment' at the bottom of the bug webpage. | When you have entered the text and saved it you can add further attachments. Click '''Add a comment/attachment''' at the bottom of the bug webpage. |
| Line 20: | Line 14: |
| [Screenshot of file browser] | Clicking '''Browse''' will open a file browser in your ubuntu home directory. Click on the disk icon to get to the base of the file system and then the {{{var}}} and {{{log}}} folders to get to {{{/var/log}}}. |
| Line 22: | Line 16: |
| Clicking ''Browse'' will open a file browser in the home directory of the default Live CD user. | attachment:filebrowser.png |
| Line 26: | Line 20: |
| On newer systems (6.10 and 7.04) this is often the most important file and should be attached to crash reports. | On newer systems (6.10 and up) this is often the most important file and should be attached to crash reports. After installation, this is saved as `/var/log/installer/syslog`. |
| Line 30: | Line 26: |
| If the installer crashes at or beyond the partition stage, then this file is also likely to be important. | If the installer crashes at or beyond the partition stage (the re-organizing of your hard disk), then this file is also likely to be important. After installation, this is saved as `/var/log/installer/partman`. |
| Line 34: | Line 32: |
| On 6.06 versions and older the {{{/var/log/installer/syslog}}} file contains the key installer logs (later moved to {{{/var/log/syslog}}}). If you experience errors with 6.06 we would encourage you to also try the install with a later edition and add comments about that to your bug report. | On 6.06, the {{{/var/log/installer/syslog}}} file contains the key installer logs (later moved to {{{/var/log/syslog}}}). If you experience errors with 6.06 we would encourage you to also try the install with a later edition of the Ubuntu CD and add comments about that to your bug report. == /var/log/installer/debug == Sometimes a developer may ask you to reproduce a problem by running {{{ubiquity --debug}}} from a terminal, and to attach this file. It contains a full debug trace of all ubiquity's communications with debconf. |
Uploading log files after an installer crash
If you wish to provide a bug report of a crashed installer it is important to also include the relevant log files. These can be found in the Live CD file system just after the crash happened.
Filing a bug
The crash report window will pop up. It asks you to file [https://bugs.launchpad.net/ubuntu/+source/ubiquity/+filebug a bug under the ubiquity package]. Follow the instructions to add a summary and description. Please copy and paste the 'traceback' displayed, and describe what stage you were at when it crashed.
Adding an attachment
When you have entered the text and saved it you can add further attachments. Click Add a comment/attachment at the bottom of the bug webpage.
Clicking Browse will open a file browser in your ubuntu home directory. Click on the disk icon to get to the base of the file system and then the var and log folders to get to /var/log.
attachment:filebrowser.png
The /var/log/syslog file
On newer systems (6.10 and up) this is often the most important file and should be attached to crash reports.
After installation, this is saved as /var/log/installer/syslog.
The /var/log/partman file
If the installer crashes at or beyond the partition stage (the re-organizing of your hard disk), then this file is also likely to be important.
After installation, this is saved as /var/log/installer/partman.
/var/log/installer/syslog
On 6.06, the /var/log/installer/syslog file contains the key installer logs (later moved to /var/log/syslog). If you experience errors with 6.06 we would encourage you to also try the install with a later edition of the Ubuntu CD and add comments about that to your bug report.
/var/log/installer/debug
Sometimes a developer may ask you to reproduce a problem by running ubiquity --debug from a terminal, and to attach this file. It contains a full debug trace of all ubiquity's communications with debconf.
DebuggingUbiquity/AttachingLogs (last edited 2009-01-12 17:00:11 by c-24-21-50-133)