Comment 13 for bug 736500

Hendrik, do you have any ideas as to where the problem may be? I can imagine that the problem is over for you when it is not in evdev, but for me it is not! :-)

As far as I can tell now, gdk_event_get_coords() returns garbage y coordinates exactly when these events occur. Some layer between evdev and the application should be keeping state to be able to return correct coordinates, and this is probably what is going wrong. Which layer is this? Is it X, GDK, or should the application (Gimp, Xournal) do this?