Comment 5 for bug 1659310

I don't think the focus gets lost: In that trace goes to a window called "Scopes".

 [2017-01-25 16:12:57.438287] miral::Window Management: invoke_under_lock
 [2017-01-25 16:12:57.438703] miral::Window Management: advise_focus_lost window_info={name=, type=normal, state=restored, restore_rect=((503, 70), (360, 560)), children={}, min_width=0, min_height=0, max_width=16777215, max_height=16777215, width_inc=1, height_inc=1, min_aspect={0, 4294967295}, max_aspect={4294967295, 0}, preferred_orientation=15, confine_pointer=0, output_id=0}
 [2017-01-25 16:12:57.438805] miral::Window Management: advise_focus_gained window_info={name=Scopes, type=normal, state=restored, restore_rect=((523, 75), (320, 544)), children={}, min_width=320, min_height=320, max_width=16777215, max_height=16777215, width_inc=1, height_inc=1, min_aspect={0, 4294967295}, max_aspect={4294967295, 0}, preferred_orientation=15, confine_pointer=0, output_id=0}
 [2017-01-25 16:12:57.438859] miral::Window Management: raise_tree root=Scopes
 [2017-01-25 16:12:57.438903] miral::Window Management: advise_raise window_info={Scopes}
 [2017-01-25 16:12:57.439270] miral::Window Management: select_active_window hint=Scopes -> Scopes
 [2017-01-25 16:12:57.439312] miral::Window Management: ====

But the next log messages seems to be from Mir starting up...

 [2017-01-25:16:13:24.633] qtmir.screens: ScreensModel::ScreensModel
 [2017-01-25 16:13:24.644863] mirplatform: Found graphics driver: mir:mesa-kms (version 0.26.0)
 [2017-01-25 16:13:24.644948] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.26.0)