We of course hope that every install with the server installer succeeds. But of course reality doesn’t always work that way and there will be failures of various kinds. This topic is to explain how to report these failures to us in the most useful way so that we can fix the bugs causing them, and we’ll keep the topic up to date as the installer changes.
The first thing to do is to update your subiquity snap. Not only because we fix issues that cause failures over time but also because we’ve been working on features to make failure reporting easier.
As of version 19.12.1 of the installer, a failure will result in a crash report being generated, which bundle up all the information we need to fully diagnose a failure. These live in /var/crash in the installer environment, which for Ubuntu 19.10 and newer is persisted to the install media by default (if there is space). When an error occurs you are presented with a dialog which allows you to upload the report to the error tracker and offers options for continuing.
You can create a bug report based on the contents of a crash report by using the standard
apport-cli tool that is part of Ubuntu. Copy the crash report to another system, run “apport-cli /path/to/report.crash” and follow the prompts.
You can also run apport-cli in the installer environment by switching to a shell but apport won’t be able to open a browser to allow you to complete the report so you’ll have to type the URL by hand on another machine.