[Bug 1234393] [NEW] upstart-dbus-bridge never forwards events without passing --always

[Zygmunt Krynicki]

Public bug reported:

I'm trying to work on a simple upstart job that fires whenever a
specific signal is sent. I got to a point where that feature works but
ONLY when I also keep 'sudo upstart-dbus-bridge --always' stared in a
separate terminal.

Reading the documentation lead me to believe that the feature where
upstart discovers which jobs use 'start on dbus' to communicate that to
upstart-dbus-monitor is broken.

I have created a simple job as a proof-of-concept, it should, in theory,
capture all dbus signals and log them to /var/log/upstart/$jobname.log

start on dbus 
console log
task
exec /usr/bin/env

Is the documentation confusing or is upstart just broken here?

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: upstart 1.10-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct  2 22:37:15 2013
InstallationDate: Installed on 2013-10-02 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
MarkForUpload: True
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=bdbda791-4d4a-4719-848c-3be31345bbf4 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: init (upstart 1.10)
UpstartRunningSystemVersion: init (upstart 1.10)
upstart.upstart-event-bridge.log: upstart-event-bridge: Disconnected from Upstart

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug package-from-proposed saucy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1234393

Title:
  upstart-dbus-bridge never forwards events without passing  --always

Status in “upstart” package in Ubuntu:
  New

Bug description:
  I'm trying to work on a simple upstart job that fires whenever a
  specific signal is sent. I got to a point where that feature works but
  ONLY when I also keep 'sudo upstart-dbus-bridge --always' stared in a
  separate terminal.

  Reading the documentation lead me to believe that the feature where
  upstart discovers which jobs use 'start on dbus' to communicate that
  to upstart-dbus-monitor is broken.

  I have created a simple job as a proof-of-concept, it should, in
  theory, capture all dbus signals and log them to
  /var/log/upstart/$jobname.log

  start on dbus 
  console log
  task
  exec /usr/bin/env

  Is the documentation confusing or is upstart just broken here?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 22:37:15 2013
  InstallationDate: Installed on 2013-10-02 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=bdbda791-4d4a-4719-848c-3be31345bbf4 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)
  upstart.upstart-event-bridge.log: upstart-event-bridge: Disconnected from Upstart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1234393/+subscriptions