Drop usage of udev-bridge via events-bridge
Bug #1409129 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| upstart (Ubuntu) |
New
|
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-
instead of current:
:sys:block-
Related branches
lp://staging/~xnox/update-notifier/lp1409129
- Martin Pitt: Approve
- James Hunt: Pending requested
- Ubuntu Core Development Team: Pending requested
-
Diff: 29 lines (+6/-2)2 files modifieddebian/update-notifier-cds.conf (+3/-1)
debian/update-notifier-hp-firmware.conf (+3/-1)
lp://staging/update-notifier/ubuntu
- Dennis Kaarsemaker: Pending requested
- Diff: 0 lines
| Changed in update-notifier (Ubuntu): | |
| status: | New → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in update-notifier (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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