seb128, I think the question should be, what's a realistic timeline for
a fix in GIO?
I was sympathetic to workarounds for the sake of Trusty (and, for that
reason, did one in indicator-datetime). But now that the window for
landing things in Trusty has passed, workarounds lose a lot of their
What upstart file watcher? Upstart doesn't magically watch all files,
you have specify what you want to be notified about, and I don't think
we have a job watching e.g /usr/local/share/applications at the moment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This shows up in the daily testing too:
http://ci.ubuntu.com/power/eventstat/image/3138/machine/6/task
/indicator-messages-service/details/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308130
Thanks Colin, that's the same issue than bug #1296233
Without improving/fixing/replace inotify we mostly have workaround
solution. One would be to create those directories on the default
image...
** Changed in: indicator-messages (Ubuntu)
Importance: Undecided = Low
** Changed in:
OK, I understand. My concern is that we do have a lot of processes doing
this kind of polling, so the cumulative effect of the same root issue is
causing a lot of unwanted wakeups on a so called idle system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Right, that's a valid concern. The issue is that some code needs to
watch for new files/directories (like the desktop needs to pick new
applications when they get installed), and we don't have anything better
than inotify to do that at the moment.
Our options seem to:
- work on something better
how about you make the indicator (ab)use upstart for this, it has file
watchers already and could send an event the indicator could pick up
(hoping that systemd offers something equivalent indeed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Oliver, it would be surprising if upstart wouldn't get the same issue.
The problem here is that the mechanism provided by the kernel (inotify)
is not handling those usecases in a nice way, what client is using the
interface is not going to change that, you are just going to move the
wakeups to
what i meant is that the upstart file watcher is running anyway ... so
you could as well just use it and not have the indicator duplicate the
file watching functionality
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
