GDK_BUTTON_MOTION_MASK appears to be broken

Bug #491732 reported by Carl Karsten
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Critical
gtk+2.0 (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: dvswitch

copy of:
http://bugs.debian.org/555030
https://bugzilla.gnome.org/show_bug.cgi?id=601473 [Critical,Resolved: fixed]

Package: libgtk2.0-0
Version: 2.18.3-1
Severity: important

DVswitch has a custom widget which supports drag selection and
extension, so its event mask is:

    GDK_BUTTON_PRESS_MASK | GDK_BUTTON_RELEASE_MASK
    | GDK_BUTTON1_MOTION_MASK | GDK_BUTTON2_MOTION_MASK

It also adds and removes modal grab as the mouse button is pressed and
released, so that it can detect the end of a drag outside the window.

Today I found that this widget no longer receives motion events, only
press and release events. Adding GDK_POINTER_MOTION_MASK brings back
motion events, but I do not want to receive them while no buttons are
pressed! This is a regression from 2.16, possibly resulting from the
extensive changes to support XInput.

Ben.

ProblemType: Bug
Architecture: i386
Date: Thu Dec 3 00:17:34 2009
DistroRelease: Ubuntu 10.04
Package: dvswitch 0.8.3.1-1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-6.8-generic
SourcePackage: dvswitch
Tags: lucid
Uname: Linux 2.6.32-6-generic i686

Revision history for this message
Carl Karsten (carlfk) wrote :
affects: dvswitch (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, it has been fixed upstream in git now!

Changed in gtk+2.0 (Ubuntu):
status: New → Triaged
status: Triaged → New
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Fix Committed
Revision history for this message
Carl Karsten (carlfk) wrote :

Does that mean it will be fixed in Lucid?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is fixed in lucid indeed

Changed in gtk+2.0 (Ubuntu):
status: Fix Committed → Fix Released
Changed in gtk:
importance: Unknown → Critical
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.