You can try something like: "sleep 10; xprop", open the pop up and then click it
On Wed, Jul 8, 2015 at 12:24 PM, Martin <[email protected]> wrote: > I use VidyoDesktop regularly for conferences, but it doesn't work with > qtile. > > The problem is, that certain dialog boxes will close immediately if I > attempt to open them. > This makes me unable to operate the program. > > The event goes like this > > 1. I click on a list item to open the dialogue (eg connect) > 2. Qtile attempts to render the dialogue > 3. The dialogue gets focus, main application losses focus and it closes the > dialogue immediately. > 4. Dialogue is closes immediately > > I have attached a screenshot of how the dialogue behaves in Gnome 3. > > If I run debug in qsh, I can get the following from the log when I click: > > 2015-07-08 10:34:41,652 INFO fire:270 Internal event: > client_mouse_enter((Window(VidyoDesktop™ - Martin - vcportal.risoe),), {}) > 41,656 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 41,657 INFO fire:270 Internal event: focus_change((), {}) > 41,665 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 42,412 DEBUG _xpoll:659 ButtonPress > 42,412 INFO _xpoll:661 Handling: ButtonPress > 42,413 INFO handle_ButtonPress:887 Ignoring unknown button: 1 > 42,413 INFO call:91 Command: function((<function > Qtile.__init__.<locals>.noop at 0x7f74c1e4c620>,), {}) > 42,417 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 42,418 INFO fire:270 Internal event: focus_change((), {}) > 42,422 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 42,424 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 42,435 INFO fire:270 Internal event: > client_mouse_enter((Window(VidyoDesktop™ - Martin - vcportal.risoe),), {}) > 42,436 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_USER_TIME > 42,503 DEBUG _xpoll:659 MapRequest > 42,504 INFO _xpoll:661 Handling: MapRequest > 42,507 INFO fire:270 Internal event: window_name_change((), {}) > 42,509 INFO fire:270 Internal event: client_new((Window(VidyoDesktop),), {}) > 42,509 INFO fire:270 Internal event: setgroup((), {}) > 42,511 INFO fire:270 Internal event: group_window_add((), {}) > 42,520 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop),), > {}) > 42,521 INFO fire:270 Internal event: focus_change((), {}) > 42,526 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop),), > {}) > 42,527 INFO fire:270 Internal event: client_managed((Window(VidyoDesktop),), > {}) > 42,529 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: _NET_WM_DESKTOP > 42,530 DEBUG updateState:281 _NET_WM_STATE: None > 42,541 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,541 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,542 DEBUG updateState:281 _NET_WM_STATE: None > 42,543 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,543 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,545 DEBUG updateState:281 _NET_WM_STATE: None > 42,550 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,550 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,551 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,551 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,578 DEBUG _xpoll:659 UnmapNotify > 42,578 INFO _xpoll:661 Handling: UnmapNotify > 42,579 INFO fire:270 Internal event: client_killed((Window(VidyoDesktop),), > {}) > 42,580 INFO _del:243 Add dgroup timer > 42,587 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 42,588 INFO fire:270 Internal event: focus_change((), {}) > 42,594 INFO fire:270 Internal event: client_focus((Window(VidyoDesktop™ - > Martin - vcportal.risoe),), {}) > 42,595 DEBUG _xpoll:659 UnmapNotify > 42,595 INFO _xpoll:661 Handling: UnmapNotify > 42,596 DEBUG _xpoll:659 UnmapNotify > 42,596 INFO _xpoll:661 Handling: UnmapNotify > 42,599 DEBUG _xpoll:659 DestroyNotify > 42,599 INFO _xpoll:661 Handling: DestroyNotify > 42,599 DEBUG _xpoll:659 DestroyNotify > 42,599 INFO _xpoll:661 Handling: DestroyNotify > 42,601 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,601 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,602 DEBUG updateState:281 _NET_WM_STATE: None > 42,603 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,604 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,605 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,605 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 42,606 DEBUG updateState:281 _NET_WM_STATE: None > 42,614 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_OPAQUE_REGION > 42,614 INFO handle_PropertyNotify:1159 Unknown window property: > _NET_WM_OPAQUE_REGION > 43,540 INFO fire:270 Internal event: > client_mouse_enter((Window(martin@norad2: ~),), {}) > 43,545 INFO fire:270 Internal event: client_focus((Window(martin@norad2: > ~),), {}) > 43,546 INFO fire:270 Internal event: focus_change((), {}) > 43,552 INFO fire:270 Internal event: client_focus((Window(martin@norad2: > ~),), {}) > 45,398 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_USER_TIME > 45,894 DEBUG handle_PropertyNotify:1119 PropertyNotifyEvent: > _NET_WM_USER_TIME > > The main observation is that qtile receives a kill instruction 150 ms after > the button click is received. > > I think that some applications have dialoges which are designed to close if > the user click anywhere but in the dialoge. Qtile changes focus in a > different way and this makes the applications think that the user changed > focus and the dialogue should close. I have similar issues with dialog boxes > in matlab. > > Does anyone have suggestions to how I can approach this problem? I cannot do > a xprop to trace the class of the dialogue box (not even in Gnome) as it > closes immediately if activity occurs outside the dialogue box. > > -- > You received this message because you are subscribed to the Google Groups > "qtile-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qtile-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
