https://bugzilla.novell.com/show_bug.cgi?id=466275 User sreeves@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=466275#c22 Scott Reeves <sreeves@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@novell.com --- Comment #22 from Scott Reeves <sreeves@novell.com> 2009-02-02 17:31:53 MST --- What is happening on the front end is that we are listening to the NetworkStateChanged signal which is being emitted spuriously. We queue up an idle callback (currently the idle timeout is 5 minutes) and when this fires it asks the backend if it should check for updates. The backend replies "not time yet" so we don't check and the backend shuts down. Hence the entries in the log showing the backend coming up and going down (and doing nothing else) every 5 minutes. The real issue is why is packagekitd emitting the signal repeatedly when it shouldn't be. The backend is basing it's signal emission off libnm_glib_register_callback and it seems to be firing when the network state has not changed. I am looking into whether this is a bug or if there are other events that are supposed to cause this callback to fire. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.