Ubuntu
upstart package

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

Bug #1578288 reported by Hans Ginzel on 2016-05-04

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	upstart (Ubuntu)	Confirmed	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

Tags:

Revision history for this message

Hans Ginzel (hans-matfyz) wrote on 2016-05-04:

Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (34.9 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (135 bytes, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-06-14:

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

Changed in upstart (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuupstart package