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 Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1674477 Title: gnome screenshot gtk-mir crashes on taking the shot under Mir Status in Canonical System Image: New Status in gnome-screenshot package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging then export GDK_BACKEND=mir launch from command line: gnome-screenshot -- --desktop_file_hint=org.gnome.Screenshot.desktop Attempt to take a screen shot in any form and it will crash (see attached log) according to attente: gnome-screenshot crashes is because it delegates the screenshotting to org.gnome.Shell, and falls back to using x11 if that fails so i think the solution is to have u8 implement that interface... https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
