killprocs kills upstart-managed jobs

Bug #545412 reported by komputes on 2010-03-23
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: upstart

Running the command "sudo telinit 1" causes the computer to:
1) Display a TTY screen with cascading error messages
2) Displays xsplash
3) Displays a text underscore cursor in the top left corner

Expecting: "sudo telinit 1" should start the first runlevel which displays the recovery mode menu (or alternatively a root shell in some distros).

ProblemType: Bug
Architecture: i386
Date: Tue Mar 23 16:25:11 2010
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.5-5
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: upstart
Uname: Linux 2.6.32-17-generic i686

komputes (komputes) wrote :

I think the problem here is simply that killprocs (on entering runlevel 1) kills all Upstart-managed jobs, including Plymouth - so plymouth is not cleanly shutdown, restoring the console

If you press Alt+F1, or Alt+F7, do you find the sulogin shell?

summary: - [Lucid Beta] telinit does not switch runlevels properly
+ killprocs kills upstart-managed jobs
affects: upstart (Ubuntu) → sysvinit (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in sysvinit (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers