[17:45] <mterry> Is there a trivial way to get Mir to spew all sorts of debugging info?  (trying to see why QMirServer fails to start)  -- do I still have to set all sorts of MIR_SERVER_XXX_REPORT=log variables?
[17:49] <kdub> mterry, afaik, there's no 'turn on all the logs' option
[17:50] <mterry> kdub: is there even an easy way to see the separate options?  u-s-c --help I guess?
[17:51] <kdub> I think that would work, or else mir_demo_server --help
[17:52] <mterry> kdub: thx will do -- I don't have concrete suggestions for fixing this, but each time I have to do this, I spend a little figuring out what the names are again and then setting a bunch of options
[17:54] <mterry> It's not an easy problem, since each debugging case probably wants a separate set of variables
[17:54] <mterry> But just finding out what to set is a pain
[17:54] <mterry> And if I didn't know how to translate --help output into a set of variables, I'd be very lost
[18:01] <alan_g> If only it were up to date: https://unity.ubuntu.com/mir/component_reports.html