Comment 2 for bug 1116680

What seems to be happening is that after the moonshot ui displays an id and sends one, it exits. So, the dbus name is unbound, so messages sent to that name fail. The libmoonshot code needs to restart the service if needed. The UI may also need to stick around for a bit (without window) to avoid huge churn under high load.

What I suspect happened when we tested is that the ui was run manually and didn't exit when the ID card was sent.