Introduction

The first few times you have to report a problem with a debian installer image not installing can be frustrating as switching to a tty and using ubuntu-bug is not possible in the limited busybox session but this allow for the alternate install for lubuntu on the oldest machines to work. Getting the debug information when this breaks can be frustrating. However, to triage these bugs without logs is really hard to get the developers the info needed.

How to file

IN debian installer pressing the

With debian-installer ubuntu-bug from a shell will not work. The debian-installer busy box enviorment is quite limited in what commands you can use. Even commands like less are not available. There are a few options available here that work well. 1. Download the debug logs from another computer on the lan.

1. mount a filesystem save the debug files onto this filesystem boot a working system with that system and attach the saved logs.

How to get to the menu to enable saving debug logs. After failing the alternate installer will usually flash a red screen saying it had failed. If you still get that you may need to get back to a main menu by pressing the go back button.

1. From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run wget -r on the ip address from the machine failing to install.

1. From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run wget -r on the ip address from the machine failing to install which will save all the debug files. Otherwise you will need to dowload and save these files manually.

Then since ubuntu-bug does not work in the busy box enviornment from this computer open a webbrowser and login to https://launchpad.net and go to https://launchpad.net/ubuntu/+source/debian-installer and press the report bug button. Then enter in your bug report and attach all the files saved as debug logs. Currently launhcpad lets me attach one file per comment manually.

2.

Bug tags

Bug tags specific to the package or area should be included here for reporters so they can tag their bug report. It will also be useful for triagers. The Bugs/Tags wiki page should then be modified to include these tags.

Debugging procedure

In depth debugging procedures for this particular package or subsystem. This usually is information about the log files to gather and what to look for in them.

How to Triage

Information that will facilitate the triaging of bugs for this package or subsystem. Remind triagers of the bug tags in use for this particular package.

Stock Reply

A stock reply to be used for initial bug reports basically asking for the stuff in "How to file". The Bugs/Responses page should include this reply.

How to Forward

In the event that the package or subsystem has an upstream bug tracker this section should contain detailed steps to forward a bug to that tracker. Some packages may just link to the general "How to Forward" page for another bug tracker like Gnome's bugzilla or freedesktop.org's bug tracker.

Known bugs

Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'.

Open

Closed

Non-bugs

How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.

CategoryBugSquad CategoryDebugging