:sys: events are not propagated to user session jobs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
New
|
Undecided
|
James Hunt |
Bug Description
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.
Since this is a documented feature in http:// upstart. ubuntu. com/cookbook/ #upstart- event-bridge , I think that's a regression.