Depends on upstart-bin

[Shahar Or]

Should not depend on upstart-bin, right?

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xfce4-indicator-plugin 2.3.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Apr 5 14:22:52 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-10-12 (1635 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: xfce4-indicator-plugin
UpgradeStatus: Upgraded to vivid on 2014-11-11 (144 days ago)

[Launchpad Janitor (janitor)]

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

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

Why should it not depend on upstart-bin? The indicator services are started via upstart by the indicator plugin.

[Shahar Or (mightyiam)]

I guess I'm wrong, then.

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

Closing this report.

[Timo (friedrich-timo)]

I don't get it either why the indicator plugin needs upstart. I wanted to remove upstart and I haven't till now, because xfce4 indicator plugin tells me it needs it. But why do I need upstart if I use systemd? Just because of that plugin?

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

As of now, this plugin depends on upstart as session init to manage the indicator services. In this case, upstart acts like a standard process and does not interfere with systemd which is the system init ( (PID 1).