GNOME Bugzilla – Bug 694771
menus broken in 3.7.10
Last modified: 2013-03-05 10:51:48 UTC
With 3.7.10, I'm seeing broken behaviour where the highlight is not following the mouse beyond the first menu I'm opening in a menubar. It is not working in context menus either. Clicking on menuitems still triggers the action.
*** Bug 694459 has been marked as a duplicate of this bug. ***
More data points: - the GTK commit that breaks this is between 69f457426ae2a7b1e2cb8e74034a636831aae079 (good) and 0def26ecf1834c1ca916328460263dede160611a (bad). I wasn't able to bisect it down to the exact commit, since some of the commits in between don't work/don't build, but this should narrow it down quite a bit. - with GTK master, the bug doesn't reproduce with Mutter 3.7.5.
Created attachment 237651 [details] [review] Always send _NET_WM_FRAME_DRAWN for newly created windows Send a _NET_WM_FRAME_DRAWN for each newly created window, as required by the specification. This avoids a race where a window might be created frozen but already unfrozen by the time we first see fetch the counter value. Remove a duplicate call to meta_compositor_set_updates_frozen() which was called before the MetaWindowActor is created and hence did nothing.
Reassigning to Mutter
Review of attachment 237651 [details] [review]: Code makes sense I have no idea how to reproduce the bug to verify that it actually works though. So assuming you did that it is fine (with the comment fixed, see below). ::: src/compositor/meta-window-actor.c @@ +1563,3 @@ + /* If a window doesn't start off with updates frozen, we should + * we should send a _NET_WM_FRAME_DRAWN immediately after the first drawn. "we should" once is enough ;)
(In reply to comment #5) > Review of attachment 237651 [details] [review]: > > Code makes sense I have no idea how to reproduce the bug to verify that it > actually works though. On my system, opening a menu (especially context menus in nautilus) is usually enough to reproduce. The patch fixes it for me.