Obviously you shouldn't use SIGKILL unless you've concluded an app is broken and not responding. The polite thing to do before that is SIGTERM (which is at least catchable).
I agree Mir needs some kind of "quit" event. We need something to communicate from the shell to the app/surface that the user wants it closed cleanly and politely, but still giving the app a chance to pop up a dialog or do whatever it wants before shutdown. Mir presently lacks anything like a "quit" or "close" message from server-to-client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319582 Title: 'Failed to start RenderThread' after opening/closing applications To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1319582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
