I think the fix is:
--- a/gdk/mir/gdkmireventsource.c
+++ b/gdk/mir/gdkmireventsource.c
@@ -311,7 +313,7 @@ handle_motion_event (GdkWindow *window, const
MirMotionEvent *event)
case mir_motion_action_up:
event_type = event->action == mir_motion_action_down ? GDK_BUTTON_PRESS
: GDK_BUTTON_RELEASE;
changed_button_state = button_state ^ event->button_state;
- if ((changed_button_state & mir_motion_button_primary) != 0)
+ if (changed_button_state == 0 || (changed_button_state &
mir_motion_button_primary) != 0)
generate_button_event (window, event_type, x, y, GDK_BUTTON_PRIMARY,
modifier_state);
if ((changed_button_state & mir_motion_button_secondary) != 0)
generate_button_event (window, event_type, x, y, GDK_BUTTON_SECONDARY,
modifier_state);
I'm EOD - will pick this up tomorrow unless someone else wants to look
at it.
** Also affects: gtk+3.0 (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: gtk+3.0 (Ubuntu Vivid)
Importance: High
Assignee: Robert Ancell (robert-ancell)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388875
Title:
[gtk-mir-backend] Clicking seems to confuse GTK (or the shell)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1388875/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
