Comment 2 for bug 1478574

I'm also finding my MX4 incredibly slow, occasionally. Ususally, things are running along smoothly, but every now and then, everything freezes for seconds, typing is delayed by at least 1-2 seconds, app-loading, forget it...

I've managed to switch to terminal during some of these events and, in "top", seen dbus-daemon consuming a LOT of CPU at these times. (>50% CPU). With 4 days uptime, I see dbus-daemon have consumed 294 minutes (almost 5 solid hours) of CPU-time. A LOT more than, for example unity. Also, during regular light use, dbus-daemon is consuming ~2% CPU.

Is there any easy way to run dbus-monitor in the background, saving to some compressed file, in order to see what type of messages are produced over a period of time?