Merge lp://staging/~xnox/indicator-sound/unbreak-ubiquity into lp://staging/indicator-sound/14.04

FAILED: Continuous integration, rev:407
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https://code.launchpad.net/~xnox/indicator-sound/unbreak-ubiquity/+merge/198170/+edit-commit-message

http://jenkins.qa.ubuntu.com/job/indicator-sound-ci/80/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/indicator-sound-trusty-amd64-ci/20
    SUCCESS: http://jenkins.qa.ubuntu.com/job/indicator-sound-trusty-armhf-ci/19
        deb: http://jenkins.qa.ubuntu.com/job/indicator-sound-trusty-armhf-ci/19/artifact/work/output/*zip*/output.zip

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/indicator-sound-ci/80/rebuild

I don't think we need the DBus activation. If it is started by the XDG Autostart or Upstart, it seems that should cover all cases.

Also, we should drop the NoShowIn in the XDG Autostart file for Unity as it would get picked up by the override.

Yes, we don't need all three. Looking into it more, I think we actually want: upstart & dbus activation.

XDG Autostart was not used in any of the previous releases, and neither lightdm nor ubiquity spawns gnome-session/upstart-user-session to autostart them. So I think upstart jobs + dbus activation should cover all cases, without imposing upstart to use the indicators. (but upstart is used where possible, which all Ubuntu standard flavours).

I'll priorities to get dbus-upstart activation done rather sooner than later, to close the gap between dbus-activation & upstart job.

Are you ok to reintroduce dbus activation? (that service file will be needed to integrate with dbus-activation as well, it will simply gain additional UpstartJob=indicator-sound)

W.r.t. upstart-job itself, I would have expected indicators to start on "started indicator-service" and stop on "stopped indicator-service", why is there an artificial sync point "indiator-services-start|end" ? is it reliably emitted when indicator-service dies?