Errors entering single-user mode; hang going back to multiuser
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
Several wrong-looking messages appear when entering single-user mode,
and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode
(the graphical login never apperas, nor does the virtual-terminal login prompt).
I observed this testing with virtualbox. Haven't tried bare metal.
I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit.
But the bits which seemed relevant are reproduced below;
STEPS TO REPRODUCE:
1. Log in as root from a virtual console (in virtualbox: <host>-F1 and log in)
2. $ shutdown now # documented to enter single-user mode
/lib/init/
...
ModemManager ... Caught signal, shutting down...
ModemManager ... Could not acquire the 'org.freedeskto
3. When prompted, enter root password
...
4. ^D (or type 'exit')
...
/lib/init/
systemd-logind: Failed to start user service: Unknown unit: user@108.service
systemd-logind: Failed to start user service: Unknown unit: user@0.service
systemd-logind: Failed to start user service: Unknown unit: user@1000.service
* Starting shoopsie shoopsie [fail]
(HANGS)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: upstart 1.13.2-0ubuntu7
ProcVersionSign
Uname: Linux 3.18.0-11-generic x86_64
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 27 15:46:46 2015
InstallationDate: Installed on 2015-01-02 (25 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150102)
ProcKernelCmdline: BOOT_IMAGE=
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningS
UpstartRunningS
Changed in upstart (Ubuntu): | |
importance: | Undecided → Critical |
Changed in upstart (Ubuntu): | |
importance: | Critical → High |
Status changed to 'Confirmed' because the bug affects multiple users.