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
I assume that the GLIB-Critical messages can be avoided by adding some
statements to reset the IDs in the source to prevent calling
g_source_remove with an id that was already removed once:
e.g. for consolekit:
ck-job.c
if (job-priv-out_watch_id 0) {
g_source_remove
Errors in my syslog only started after upgrade to 14.04. I noticed it
immediately as a) I check my logs regularly and b) it's bulking out my
syslogs in terms of size on disk
May 18 07:55:33 R2D2 console-kit-daemon[875]: GLib-CRITICAL: Source ID 1660 was
not found when attempting to remove it
May
Hi johnnyb0y,
Your system feeling lethargic is unlikely to be related to the GLib-CRITICAL
warnings appearing in the logs.
They are just coincidental.
Check the output of `top` for heavy processes. In particular upgrade to
14.04 starts a very heavy new search indexing process called
** Summary changed:
- console-kit-daemon related ssh session hang w/ Glib-CRITICAL warning
+ console-kit-daemon session hang (sometimes w/ Glib-CRITICAL warning)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
