This bug was fixed in the package update-notifier - 3.160
---
update-notifier (3.160) vivid; urgency=medium
* ./debian/update-notifier-cds.conf: Stop asking udisks 1 for the
mountpoint, just awk /proc/mounts for the mount point. (LP: #1411987)
-- Martin PittTue, 20 Jan 2015
Ah, thanks Dimitri!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411987
Title:
update-notifier uses udisks1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
** Branch linked: lp:update-notifier
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411987
Title:
update-notifier uses udisks1
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Changed in: update-notifier (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411987
Title:
update-notifier uses udisks1
To manage notifications abo
On 20 January 2015 at 09:20, Martin Pitt wrote:
> I tried upstart-monitor in both default and "-d system-socket" mode, and
> it never displays anything. Ejecting/reinserting a CD ROM does not
> trigger /usr/share/upstart/sessions/update-notifier-cds.conf either. I
> *do* see the events in "sudo up
I tried upstart-monitor in both default and "-d system-socket" mode, and
it never displays anything. Ejecting/reinserting a CD ROM does not
trigger /usr/share/upstart/sessions/update-notifier-cds.conf either. I
*do* see the events in "sudo upstart-monitor" which suggests that the
system -> session
FTR, here's how to simulate this in QEMU:
- start with an empty drive: -drive media=cdrom -monitor stdio
- "insert CD": change ide0-cd0
/home/martin/Downloads/ubuntu/vivid-desktop-amd64.iso
- "remove CD": eject ide0-cd0
Unfortunately upstart doesn't seem to have any logging (in
.cache/upstart) f
