So quick brain dump. This is due to the unity8-greeter process being SIGSTOPPED while not active, seemingly due to Mir lifecycles. While sleeping, the snap decision Notify call apparently gets "stuck" in the dbus pipe and still delivered afterward, even if the source of the notification does a close() on it.
But the unity8 shell does *not* get SIGSTOPPED when inactive. And for that matter, unity8-greeter doesn't always have this problem either, which is why this bug isn't 100% reproducable. So some piece of logic is keeping the unity8 shell active. The greeter should probably do the same thing. Alternately, we could figure out why the Notify call is stuck in the dbus socket and stop that from happening. But the above is also useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327257 Title: Impossible to place snap decisions on greeter while screen is unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/unity-notifications/+bug/1327257/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
