:sys: events are not propagated to user session jobs

[You-Sheng Yang]

Starting from upstart version 1.13.2-0ubuntu6, user session jobs receive no more :sys: prefixed events. For example,

1) if a user session job A starts with following condition:

  start on (:sys:started JOB=ofono) and (started dbus)

that job A will never get started because it will never have (:sys:started JOB=ofono) received even though the (started dbus) part is still valid.

2) another similar user session job B starts with:

  start on :sys:started JOB=ofono

will never get started, neither.

3) yet another user session job C:

  start on started dbus

will work as expected.

4) further more, a user session job D starts with:

  start on :sys:started

is never executed.

5) a _system_ job E with:

  start on started

will be executed.

Tested on vivid-armhf, ubuntu phone.

[You-Sheng Yang (vicamo)]

Since this is a documented feature in http://upstart.ubuntu.com/cookbook/#upstart-event-bridge , I think that's a regression.

[You-Sheng Yang (vicamo)]

https://launchpad.net/ubuntu/+source/upstart/1.13.2-0ubuntu6

[Steve Langasek (vorlon)]

It's not a regression because it's a deliberate behavior change. This will need to be addressed by updating the cookbook.

[You-Sheng Yang (vicamo)]

Here's a list of affected packages:

  $ for f in `grep -nr ^start\ on\ .\*:sys: /usr/share/upstart/sessions/| cut -d: -f1`; do dpkg -S $f; done
  upstart-bin: /usr/share/upstart/sessions/logrotate.conf
  mtp-server: /usr/share/upstart/sessions/mtp-server.conf
  nuntium: /usr/share/upstart/sessions/nuntium.conf
  ubuntu-touch-session: /usr/share/upstart/sessions/ofono-setup.conf
  upstart-bin: /usr/share/upstart/sessions/re-exec.conf

[You-Sheng Yang (vicamo)]

With bug https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1413316 patched package ubuntu-touch-session, the affected list I can find reduces to mtp-server, nuntium, and upstart-bin itself.