Drop usage of udev-bridge via events-bridge

Bug #1409129 reported by Dimitri John Ledkov on 2015-01-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Undecided
Unassigned
upstart (Ubuntu)
Undecided
Unassigned

Bug Description

Currently there is udev-bridge that connects to system upstart and emits "*-device-changed" events and related. User session init has an events bridge that connects to system upstart and listen on event, and re-emits them to session upstart.

udev socket <- udev-bridge -> system upstart <- events-bridge -> session upstart

But when system upstart is gone, this falls apart... thus I'm proposing to run udev-bridge on the session-upstart

udev socket <- udev-bridge -> session upstart

This would mean that udev events on the session upstart can be interpreted as:

block-device-changed

instead of current:

:sys:block-device-changed

Related branches

Martin Pitt (pitti) on 2015-01-16
Changed in update-notifier (Ubuntu):
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-notifier - 3.159

---------------
update-notifier (3.159) vivid; urgency=medium

  [ Dimitri John Ledkov ]
  * Prepare for udev-bridge on the session bus. (LP: #1409129)
 -- Martin Pitt <email address hidden> Fri, 16 Jan 2015 18:59:51 +0100

Changed in update-notifier (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers