[Bug 1313042] Re: console-kit-daemon Glib-CRITICAL warning

[Ariel Faigon]

I figured the reason for my hangs was unrelated to the GLIB warning.
I had a sub process of the main job blocking on stdin input when arguments were missing, the main job was waiting for the sub process to finish so it didn't exit(1).  Bottom line:  the "hang" cause was a silly bug in one of my own scripts.  Sorry about that.

So there's no hang issue in this bug - there's only a GLIB misuse and
console warning.

I updated the bug description to be shorter/simpler accordingly.

I consider the severity/priority much lower now.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to consolekit in Ubuntu.
https://bugs.launchpad.net/bugs/1313042

Title:
  console-kit-daemon Glib-CRITICAL warning

Status in “consolekit” package in Ubuntu:
  Confirmed

Bug description:
  The day I upgraded from 13.10 to 14.04 some of my ssh sessions into
  the new system (server side is Ubuntu 14.04) started hanging.

  The symptom is: I run some command with a lot of output (say a few
  hundreds of lines) in an ssh session, and the second the command
  completes, and the shell displays a new  prompt, the shell stops
  responding to keyboard input.

  At  the exact time of the hang (to the second) I always see these 3
  warnings in syslog:

  Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 469 was not found when attempting to remove it
  Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 86 was not found when attempting to remove it
  Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 86 was not found when attempting to remove it

  The Source ID numbers vary, but the warnings always come in triplets
  at the time of the hang.   I was able to reproduce this about 10 times
  today.  Every time the session hangs, these warnings appear in the log
  and vice versa: every time they appear in the log, I have a hanged
  remote session.

  A 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 based on this I'm opening a bug against  consolekit for bad calls
  to g_source_remove() which seem to be related to the ssh hang.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1313042/+subscriptions