Ubuntu 17.10.1 fails to reboot after installation is complete

Bug #1754328 reported by Panos Georgiadis on 2018-03-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

How to reproduce:
------------------
1. Download the ISO for 17.10.1 from the official website
2. Create a virtual-machine with qemu and load the ISO to start the installation

Note: do a generic installation without changing any parameters (e.g. do not download updates during the installation) but use everything in default.

3. When the installation is complete, it will ask you to remove the media and press ENTER.

Expected Behavior:
------------------
The system should reboot without any problems.

Actual Behavior:
----------------
The following things are happenings:

1. It shows blank screen and stays there forever
2. It throws WATCHDOG error and stays there forever:

> systemd-journald[]: failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

3. Sometimes it works and everything is fine

Workaround:
-----------
The workaround for [1][2] is to hard-reset the qemu VM.

It looks like a race condition, that when it gets triggered it hits a bug related to watchdog and reboot of the system. Note, that this bug is **not** reproducable if you click "Try Ubuntu" at the 'welcome' screen of the 17.10.1 ISO media. You have to actually install it and make it to the last step of the installation, which is the restart of the system.

description: updated

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1754328/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Panos Georgiadis (drpaneas) wrote :

The bug is against the Ubuntu installer. I don't know what is the package of this component and I cannot get a console (I'e tried all tty's but no luck). Given that installation issues are quite common, I would expect you to link bugs against 'components' instead of 'source packages'.

Paul White (paulw2u) on 2018-03-08
affects: ubuntu → ubiquity (Ubuntu)
Panos Georgiadis (drpaneas) wrote :

Thanks @paulw2u for linking the source package. I've never heard of Ubiquity before, so I also learned something new today :D https://wiki.ubuntu.com/Ubiquity

tags: added: ubiquity
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers