No mouse, no keyboard after upgrading from 16.04.1 to 16.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Install Ubuntu 16.04 upgrade to latest 16.04.1.
Make sure in /etc/update-
"Prompt=normal" is set.
Then as root:
# do-release-upgrade
Answer all questions with "y". The release upgrade will take place.
After it is finished it will ask a last question about rebooting.
Answer "y". The system will reboot.
After printing
Ubuntu 16.10 <hostname> tty1
<hostname> login:
for a short time the cursor blinks after ":". It vanishes.
You'll wont have keyboard, you'll wont have mouse.
CTRL-ALT-DEL wont work.
sshd will never start.
The system is dead until you reset it. It will boot again, but again no keyboard, no mouse.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.4.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
Date: Mon Oct 24 17:21:52 2016
InstallationDate: Installed on 2014-01-31 (997 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-
Symptom: release-upgrade
UpgradeStatus: Upgraded to xenial on 2016-09-06 (48 days ago)
VarLogDistupgra
Error: command ['pkexec', 'cat', '/var/log/
Error executing command as another user: Not authorized
This incident has been reported.
Since it is not possible to report a bug from systems not accepting any keypresses or mouse actions, I used some system that does -- I used the system I wanted to upgrade. But until this issue is solved I wont upgrade! It would therefore be nice to have some instructions on how I can access the system failing the upgrade. Adding "init=/bin/bash" just puts me in a shell within "initrd" mounted as root. Not really helpful.
It is the same old thing: you cant execute "ubuntu-bug" from non accessible systems, but it seems to be the only way to file a bug report. Even if this will add various missleading files to this bug report, because these are from a RUNNING, WORKING system, not from the one NOT RUNNING, NOT WORKING.