Comment 7 for bug 1674477

> 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.

This is something I've thought about before too with gtk, and I think it comes down to whether you want your platform modular where you can pick and choose the parts you want, or you want to define your platform to be one monolithic unit. We have gtk that depends on libmirclient and content-hub, but what happens if you have a mir server but no content-hub? Should that situation be possible?

> That all said... why don't we just declare gnome-screenshot unsupported if it's really just a client of gnome-shell. Doesn't Unity8 have other adequate screenshotting mechanisms?

I'm wondering this too. Print screen doesn't seem to do anything in U8.

It does seem weird that it isn't just baked directly into gnome-shell since it's just a front-end for that interface. Maybe it was intended to allow gnome-screenshot to be usable on other DEs. But yes, basically do we want gnome-screenshot to work on U8? And if so, do we want that to be the default way of doing it? U8 can still decide to support gnome-screenshot even if it provides its own.