Comment 20 for bug 1185565

given how similar all the indicators are, i'm not sure why there is a unique job for each one:

instance $INDICATOR
export INDICATOR
start on indicators-loaded or indicator-services-start
stop on desktop-end or indicator-services-end
respawn
exec /usr/lib/x86_64-linux-gnu/indicator-$INDICATOR/indicator-$INDICATOR-service

and then something else, e.g. can decide which indicators are wanted and simply do:
start indicator INDICATOR=sound

Such that to avoid boilerplate indicator-*.conf jobs. Each instance can individually be stopped, startered, restarted and gets it's own log file....

Similarly there is upstart-dbus-bridge, such that instead the indicators can do "start on dbus INTERFACE=com.ubuntu.foo", so I don't think removing dbus activation gains us anything, so far it only broke showing indicators in the ubiquity-dm and non-upstart mananged user-sessions where indicators can be used. At the moment, all user sessions on the desktop can be fully started without being managed by upstart and users can disable that.