#203 ButtonRelease event is off-screen

closed-invalid
nobody
2011-10-04
2011-10-03
No

In Fedora 15 with latest updates (running wacom driver 0.11.1) (64-bit version if it matters), ButtonRelease events occur at the wrong coordinates. This sounds possibly similar to the closed bug "Tablet button input moves cursor to top left of screen - ID: 3367196".

Selected xev output:

ButtonPress event, serial 33, synthetic NO, window 0x3600001,
root 0xb9, subw 0x0, time 54987493, (93,66), root:(2017,91),
state 0x10, button 1, same_screen YES
MotionNotify event, serial 33, synthetic NO, window 0x3600001,
root 0xb9, subw 0x0, time 54987500, (94,66), root:(2018,91),
state 0x110, is_hint 0, same_screen YES
...
MotionNotify event, serial 33, synthetic NO, window 0x3600001,
root 0xb9, subw 0x0, time 54987713, (129,79), root:(2053,104),
state 0x110, is_hint 0, same_screen YES
LeaveNotify event, serial 33, synthetic NO, window 0x3600001,
root 0xb9, subw 0x0, time 54987713, (-4,-25), root:(1920,0),
mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
focus YES, state 16
ButtonRelease event, serial 33, synthetic NO, window 0x3600001,
root 0xb9, subw 0x0, time 54987713, (-4,-25), root:(1920,0),
state 0x110, button 1, same_screen YES

It's only the "LeaveNotify" and "ButtonRelease" events that are completely off the mark.

I am in a two-screen configuration, with the tablet mapped to the rightmost one, in case it helps.

I'll try to investigate if I find time.
Denis

Discussion

  • Denis Auroux

    Denis Auroux - 2011-10-03

    Update:

    1. this happens even in single-monitor mode, so it's NOT a dual-head issue

    2. you might have noticed already, but just in case: the LeaveNotify and ButtonRelease occur exactly at the top-left corner of the current screen.

     
  • Denis Auroux

    Denis Auroux - 2011-10-04
    • status: open --> closed-invalid
     
  • Denis Auroux

    Denis Auroux - 2011-10-04

    Problem went away after a couple of major tweaks to my xrandr config and reboots, none of which should have had any impact on this. Perhaps a sporadic isolated issue and not a real bug.

    Closing the bug until I know how to reproduce it...
    Denis

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks