Our current consolekit-0.4.6 often logs "GLib-CRITICAL: Source ID was not found" warnings to the log on various occasions. These are caused by GLib's new warning about mismatched reference counting, and as such are really bugs in applications. This was mostly fixed in the new ConsoleKit2 in the upstream commit https://github.com/ConsoleKit2/ConsoleKit2/commit/0b79d92001450e7f359212d4273100628f6a1693 , however this did not completely fix the issue. I worked with upstream to fix the last occurrence during ssh idle timeout + logout (https://github.com/ConsoleKit2/ConsoleKit2/pull/15) and we have fixed the issue. It would be good to get this into our current ck-0.4.6 ebuild until 0.9.x/1.0 is finalized. Reproducible: Always Steps to Reproduce: 1. with ck-0.4.6 e.g. log in, let tty sit idle, log out Actual Results: ck logs various GLib complaints about mismatched refcounts. Expected Results: No warnings I'll attach patches both to the ebuild and the source. Both are fairly small, one is already in 0.9.x and the other one will shortly be. I have them running locally on several machines and all GLib-CRITICAL messages are gone. Since the current (old/unmaintained) ck-0.4.6 is stable we could bump this into ~ck-0.4.6-r1 for testing, while we wait for ck2-0.9.x to become 1.0.
Created attachment 391354 [details, diff] Aggregate patch to silence GLib-CRITICAL messages
Created attachment 391356 [details, diff] Patch for ebuild to include GLib fixes
I'm closing this since this problem is fixed upstream and 1.0 is now released in ~arch.
