Ubuntu GNOME Xenial install ended with tty1 prompt

Bug #1554158 reported by Erick Brunzell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Not sure what happened here but I just installed Ubuntu GNOME Xenial 20160306 amd64 and towards the end of the install the screen went blank and displayed a tty1 login prompt. I waited a little while but nothing appeared to be responsive so I did a hard reboot. Surprisingly I was able to boot the new install afterwards but clean-up was not complete. Ubiquity was still installed so the "install release" icon is in the launcher and the live media was still clicked-on in software settings. Maybe the logs will provide some evidence of what happened.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 7 11:49:44 2016
InstallCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sdc6
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Erick Brunzell (lbsolost) wrote :
Revision history for this message
Erick Brunzell (lbsolost) wrote :

I noticed this snippet in the syslog:

Mar 7 11:07:51 lance-AMD-desktop kernel: [ 953.404371] nouveau 0000:00:0d.0: bus: MMIO write of 06490001 FAULT at 00b010
Mar 7 11:07:53 lance-AMD-desktop kernel: [ 954.715857] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b010
Mar 7 11:13:11 lance-AMD-desktop kernel: [ 1273.307058] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b020
Mar 7 11:13:51 lance-AMD-desktop AptDaemon: INFO: Quitting due to inactivity
Mar 7 11:13:51 lance-AMD-desktop org.freedesktop.PackageKit[612]: 11:13:51 AptDaemon [INFO]: Quitting due to inactivity
Mar 7 11:13:51 lance-AMD-desktop org.freedesktop.PackageKit[612]: 11:13:51 AptDaemon [INFO]: Quitting was requested
Mar 7 11:13:51 lance-AMD-desktop AptDaemon: INFO: Quitting was requested

Revision history for this message
Erick Brunzell (lbsolost) wrote :

journalerrors from the same time:

Mar 07 11:07:15 username-AMD-desktop systemd-tmpfiles[10718]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Mar 07 11:07:51 username-AMD-desktop kernel: nouveau 0000:00:0d.0: bus: MMIO write of 06490001 FAULT at 00b010
Mar 07 11:07:53 username-AMD-desktop kernel: nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b010
Mar 07 11:13:11 username-AMD-desktop kernel: nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b020
Mar 07 11:13:51 username-AMD-desktop org.freedesktop.PackageKit[612]: 11:13:51 AptDaemon [INFO]: Quitting due to inactivity
Mar 07 11:13:51 username-AMD-desktop org.freedesktop.PackageKit[612]: 11:13:51 AptDaemon [INFO]: Quitting was requested

I think everything that's shown after that is activity after booting into the fresh install.

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1554158

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → 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.