[Bug 1313042] Re: console-kit-daemon session hang (sometimes w/ Glib-CRITICAL warning)

johnnyb0y ubuntu64 at johnnyboy.cc
Mon Jun 2 19:48:36 UTC 2014


I 'bit the bullet' and decided to remove consolekit (console kit daemon)
with the following warnings:

sudo aptitude remove consolekit        
The following packages will be REMOVED:  
  consolekit 
0 packages upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 473 kB will be freed.
The following packages have unmet dependencies:
 cinnamon-session : Depends: consolekit but it is not going to be installed.
 lxsession-logout : Depends: consolekit but it is not going to be installed.
 libpolkit-qt-1-1 : Depends: consolekit but it is not going to be installed.
The following actions will resolve these dependencies:

     Remove the following packages:
1)     cinnamon-session            
2)     libpolkit-qt-1-1            
3)     libqapt2-runtime            
4)     lxde                        
5)     lxde-common                 
6)     lxde-core                   
7)     lxinput                     
8)     lxsession                   
9)     lxsession-logout            

Accept this solution? [Y/n/q/?] y
The following packages will be REMOVED:
  alien{u} cinnamon-session{a} consolekit debugedit{u} galculator{u} giblib1{u} leafpad{u} libpolkit-qt-1-1{a} libqapt2-runtime{a} librpmbuild3{u} librpmsign1{u} 
  libxmmsclient-glib1{u} lxappearance{u} lxde{a} lxde-common{a} lxde-core{a} lxinput{a} lxmusic{u} lxrandr{u} lxsession{a} lxsession-edit{u} lxsession-logout{a} 
  lxshortcut{u} menu-xdg{u} rpm{u} scrot{u} xarchiver{u} xmms2-core{u} xmms2-plugin-alsa{u} xmms2-plugin-id3v2{u} xmms2-plugin-mad{u} xmms2-plugin-vorbis{u} 
0 packages upgraded, 0 newly installed, 32 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 12.6 MB will be freed.
Do you want to continue? [Y/n/?] y

My system now responds much much quicker, my syslog doesn't get filled
with errmsgs every 15 seconds and I'm happy, although my method of
removal was fairly destructive so I wouldn't recommend it ;-)

My ssh connections remotely now work at the expected speed and I can now
log in to my box remotely from work in a couple of seconds, instead of
10 seconds plus.

-- 
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 session hang (sometimes w/ 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



More information about the foundations-bugs mailing list