installation finished gracefully, but did not reboot when told to

Bug #1225899 reported by sudodus
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Yesterday I ran saucy-desktop-amd64.iso in an Ubuntu Host running lubuntu-desktop with a not fully up to date 12.04.2 LTS.

(1) The installation proceeded as it should (it finished gracefully),

(2) I discovered, that the installed system boots to grub, but then nothing happens (only black screen in the virtual machine window).

So something seemed to be wrong. I looked more into it today.

A. I updated/upgraded the host operating system.

B. I zsynced saucy-desktop-amd64.iso (an received the next daily build).

And I tried again:

(1) The installation proceeded as it should (it finished gracefully), but *did not reboot* when told to. I had to shut down the virtual machine 'from the outside'. I think this is a bug.

(2) This time I could boot into a working installed Lubuntu 64-bit system with graphics and 'everything' works in the installed system.

The main VirtualBox specs are the following:
-----
VirtualBox version 4.1.12_Ubuntu_r77245

that comes with Ubuntu 12.04 (via the repos)

General:
Name: t1
OS Type: Ubuntu (64 bit)

System:
Base Memory: 1280 MB
Processors: 2
Execution Cap: 90%
Boot Order: Diskett, CD/DVD-ROM, Hårddisk
Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX

Screen:
Video Memory: 12 MB
Remote Desktop Server: Disabled

Storage:
IDE control card
  IDE Primär master (CD/DVD): (1) saucy-desktop-amd64.iso (695,00 MB) at
installation; (2) Empty
SATA control card
  SATA-port 0: t1.vdi (Normal, 8,00 GB)

Audio:
Host Driver: PulseAudio
Controller: ICH AC97

Network:
Adapter 1: Intel PRO/1000 MT Desktop (Bridged adapter, eth1)

USB:
Shared folders

Description:
None
-----

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 16 09:50:22 2013
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
InstallationDate: Installed on 2013-09-16 (0 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130915)
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
sudodus (nio-wiklund) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1225899

tags: added: iso-testing
Revision history for this message
sudodus (nio-wiklund) wrote :

The screen with the message (that installation has finished, and I should
reboot) remains on the screen and the cursor is the round busy one.

So it is not a black screen, it seems not to finish but 'hangs' at that
finishing screen of the installer. And I can see from the host system,
that the vbox processes are fully busy (both processors at max for hours).

Revision history for this message
sudodus (nio-wiklund) wrote :

A Toshiba [1] with Intel i5 CPU hangs in a different way. The screen with the message is closed, the graphical screen is shut down and it hangs at the text screen with one single message line:

* Asking all remaining processes to terminate... [OK]

[1] http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/

And when I press Enter, it will reboot. So in the Toshiba, it seems to be the old bug, that there is no message to remove the boot media and press Enter, bug 966480.

ThThe installation was into a CSM system (not UEFI).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
sudodus (nio-wiklund) wrote :

I think it might be the same bug as the one reported here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1227202

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.