powerd calls unity8 (via dbus) which calls mir to turn off the display. If i cut unity8 out of the loop, then powerd and mir disagree on the fb state more often because calls to change the state (originating from powerd) don't update mir.
kgunn probably didn't see any problems (and users shouldn't either) because mir and powerd start in the same state, and with unity involved, powerd notifies mir every time the display state changes. It is still a problem for testing and development because mir always starts with the assumption that it can turn on the display, even though powerd may have shut the system down. So, if unity8 crashes (or is restarted), or if you're running some of the mir test programs by themselves (like I was in comment #6), i'd expect to see this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188504 Title: Nexus4: Mir server dies when display goes to sleep ("error posting with fb device") and can no longer start ("could not unblank display") To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1188504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
