[Bug 68946] mission control can take 100% cpu if its associated dbus drop

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=68946

--- Comment #7 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
The debug log from that Mission Control, with appropriate environment variables
to get Telepathy, GDBus and GOA debug, would also be interesting.

Perhaps put this in gdm's
${XDG_DATA_DIRS}/dbus-1/services/org.freedesktop.Telepathy.AccountManager.service:

[D-BUS Service]
Name=org.freedesktop.Telepathy.AccountManager
Exec=/usr/local/libexec/debug-mc.sh

where /usr/local/libexec/debug-mc.sh is something like this:

#!/bin/bash
export G_DBUS_DEBUG=all
export G_MESSAGES_DEBUG=all
export MC_DEBUG=all
export MC_TP_DEBUG=all
exec > /var/lib/gdm/gdm-mc-$$.log 2>&1
exec /usr/libexec/mission-control-5

(and if there are magic environment variables to debug GOA, or to debug
Empathy's GOA plugin, those might be interesting too.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.