restart: Unable to connect to Upstart: Failed to connect to socket

Bug #1578288 reported by Hans Ginzel
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Undecided
Unassigned

Bug Description

Remove obsolete upstart commands from upstart package or correct the dependencies. Package unity-greeter depends on upstart. Package unity-greeter depends on unity-greeter.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: upstart 1.13.2-0ubuntu21
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
Date: Wed May 4 12:42:52 2016
SourcePackage: upstart
UpgradeStatus: Upgraded to xenial on 2016-05-03 (1 days ago)
UpstartBugCategory: Session
UpstartRunningSessionCount: 2
UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist

Revision history for this message
Hans Ginzel (hans-matfyz) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in upstart (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