On one hand asking the shell to own screenshotting is nice and secure. On the other hand, persisting with an architecture where apps don't work unless processes other than the shell happen to be running is a bit nasty in my opinion. And similarly anything that depends on a bus is ugly IMHO. I've lost count of the number of times in recent months where GTK apps refused to start because they were timing out waiting for some process or bus to become available that didn't exist in Mir.
When you develop an app for a platform, like for Mir using just libmirclient, there should ideally be zero other dependencies on the system. Everything should be implemented or proxied through that one library. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674477 Title: gnome screenshot gtk-mir crashes on taking the shot under Mir To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
