initctl cannot find Upstart

[IanG]

Please see Apport's automatically generated files (attached)

ProblemType: RecoverableProblem
DistroRelease: Ubuntu 15.04
Package: upstart 1.13.2-0ubuntu13
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 7 19:03:35 2015
DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error
ExecutablePath: /sbin/upstart
InstallationDate: Installed on 2011-12-08 (1246 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /sbin/upstart --user
SourcePackage: upstart
UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago)
UpstartBugCategory: Session
UpstartRunningSessionCount: 1
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist
UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data
icon_file: (null)
is_current_user: false
is_logged_in: false
real_name: (null)
uid: 0
upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: Connection refused
user_name: (null)

[Launchpad Janitor (janitor)]

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

[Alberto Salvia Novella (es20490446e)]

Please:
  1. Modify the bug description, so it explains how to reproduce the bug and which are its consequences.
  2. Set this bug status back to "confirmed".

Thank you.

[higuita (higuita)]

to reproduce:
 boot the machine... it show up a warning that a application had a internal error.
 Consequences... well, it is annoying, but other than that we don't see any. Maybe one less background (and possible useless) service

This machine is being upgrade since many releases, probably a new clean installs don't have it.
Maybe canonical can release a tool that shows what packages should a default ubuntu install should have (flagging the missing ones) and what packages are installed and would not been in a default install. One could then cleanup any old packages that might be messing the system

[Dimitri John Ledkov (xnox)]

Hm, that should not be logged anymore.

[IanG (ian-usts)]

Same issue again this morning on logging on.

[Sinisa Radalj (sinisa1hr)]

not only one..

[Ertan Günay (ergunay)]

I upgraded system a few days ago from 15.04 to 15.10
This morning, this problem happened.

[Brian Smith (brian-smith-i)]

After today's update to 15.10

[Ertan Günay (ergunay)]

This error happened while updating today's daily update

[Craig Errington (craigerrington)]

Clean install of 15.10 - dist-upgrade, reboot, same error.

[aljosa (aljosa-p)]

Ubuntu 16.04 - same error

[Tomasz J. Kotarba (tomasz-kotarba)]

dpkg --purge upstart libupstart1 solved this in 15.10

[craigleat (craig-leat)]

On my system (15.10) unity-greeter depends on upstart

[twicejr (twicejr)]

Happens now on 16.10 as well, on my system...

[CosmoJG (cosmojg)]

This is still an issue in 16.04.1 as of August 23rd, 2016.

[Stephan Druskat (sdruskat)]

Happened on 16.04.1, 8 Sep 2016.

[kuntergunt (kuntergunt)]

Still an issue on 16.10 upgraded a couple of times starting with 13.10