<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: focus issue with gnome-terminal" href="https://bugzilla.gnome.org/show_bug.cgi?id=748892#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: focus issue with gnome-terminal" href="https://bugzilla.gnome.org/show_bug.cgi?id=748892">bug 748892</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre> (In reply to Olivier Fourdan from <a href="show_bug.cgi?id=748892#c5">comment #5</a>) > Yet I fail to come up with a simple reproducer using gtk+ alone, not I can > find any other app that exhibit the same behaviour so maybe it's g-t > triggering that bug in gtk but I still don't know how... > [...] OK, some progress, gdb FTW. What confuses gtk+ is the use of a GtkWindowGroup. Basically what happens is that g-t creates a GtkWindowGroup for its windows and when opening a new terminal using the menu, the grab is on the menu so that gtk_main_do_event() will pick the GtkMenuBar attached to the current window and not the new window. Not using a GtkWindowGroup in g-t fixes the focus issue. I wonder why this affects Wayland and not x11 though.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>