You are not logged in.
Everyday when I boot up, I notice that the systemd-journal process is stuck at 100% cpu
When I run journalctl, I see stuff like :
Feb 19 14:32:41 archaic org.freedesktop.Telepathy.ConnectionManager.gabble[454]: (telepathy-gabble:653): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
Feb 19 14:32:41 archaic org.freedesktop.Telepathy.ConnectionManager.gabble[454]: This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
Feb 19 14:32:41 archaic org.freedesktop.Telepathy.ConnectionManager.gabble[454]: The overwriting error message was: Operation was cancelled
Feb 19 14:32:41 archaic org.freedesktop.Telepathy.ConnectionManager.gabble[454]: (telepathy-gabble:653): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
Feb 19 14:32:41 archaic org.freedesktop.Telepathy.ConnectionManager.gabble[454]: This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
Feb 19 14:32:41 archaic org.freedesktop.Telepathy.ConnectionManager.gabble[454]: The overwriting error message was: Operation was cancelledHundreds of thousands of these messages with the same timestamp, causing systemd to struggle to log it.
If I run "killall telepathy-gabble", the system settles down.
Strangely the KDE telepathy messenger seems to continue to run fine on the desktop.
How do I cure this?
My kde version is 4.12.1-1
Thanks in advance,
Vivek
Offline
Badly written software I guess. Maybe try testing, see if that helps?
Someone had it as well.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline