Ted, assigning to you since you added the upstart job.
That's something Lars warned about previous cycle, but we forgot about
it before merging, the dbus activation was letting the indicator control
if it needed to run or to exit. We profile need to make the upstart job
smarter (like maybe tweak the signal to specify the session type and
start e.g sync only in desktop mode)
Other indicators have similar issues, but they don't keep respawning
because they stopped using libindicator so they don't have the exit-
when-no-listener behaviour
** Changed in: indicator-sync
Importance: Undecided => High
** Changed in: indicator-sync
Assignee: (unassigned) => Ted Gould (ted)
** Summary changed:
- Upstart jobs keeps respawing indicator-sync on the greeter
+ Upstart job keeps respawing indicator-sync on the greeter
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sync in Ubuntu.
https://bugs.launchpad.net/bugs/1255719
Title:
Upstart job keeps respawing indicator-sync on the greeter
Status in The Sync Menu:
New
Status in “indicator-sync” package in Ubuntu:
New
Bug description:
Using trusty, /var/lib/lightdm/.cache/upstart/indicator-sync.log
indicates that upstart keeps trying spawning indicator-sync which exit
with "No watchers, service time out."
The indicator is not supposed to be used on the greeter, the upstart
job there seems like it should be smarter...
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sync/+bug/1255719/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
