Comment 6 for bug 1258655

From mir's perspective, i see "start, stop, start, stop, ..., start, start" being called on the compositor. The double start, start causes an error in the compositor. (specifically, an egl context is current in two threads, causing an error BAD_ACCESS in the second thread).

powerd-cli listen just reports the on/off/on/off pattern when the double start happens from mir's perspective. Currently digging a bit into unity-mir to see what's going on up there.