GLib recently started throwing a warning when g_source_remove()
is passed garbage (as per warning). Your applications have probably been broken
for a while, and there's no telling what could actually have happened in the
past when g_source_remove() would happily close any random source because the
programmer got the wrong argument to g_source_remove().
So if true, it looks like this should be reasssigned either to Glib, or to all the affected applications.
The problem isn't just the error (log pollution). When the error occurs, I see ssh sessions actually hang when console-kit-daemon prints the error. This is a regression in 14.04 vs 13.10.
Quote from an upstream (bugzilla. gnome.org) comment:
https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 721369
GLib recently started throwing a warning when g_source_remove()
is passed garbage (as per warning). Your applications have probably been broken
for a while, and there's no telling what could actually have happened in the
past when g_source_remove() would happily close any random source because the
programmer got the wrong argument to g_source_remove().
So if true, it looks like this should be reasssigned either to Glib, or to all the affected applications.
The problem isn't just the error (log pollution). When the error occurs, I see ssh sessions actually hang when console-kit-daemon prints the error. This is a regression in 14.04 vs 13.10.