https://bugs.kde.org/show_bug.cgi?id=377901
--- Comment #10 from Kenneth Lakin <kennethla...@gmail.com> --- (In reply to Martin Gräßlin from comment #9) > Some additional investigation results: both moving windows and Alt+Tab > require a keyboard/pointer grab. The xTime() is going into those requests > and the documentation says: > > "The request fails with status InvalidTime if the specified time is earlier > than the last-pointer-grab time or later than the current server time. > Otherwise, the last-pointer-grab time is set to the specified time, with > CurrentTime replaced by the current server time." I may be out of my depth (or reading the wrong documentation), but this quote seems relevant: "A timestamp is a time value, expressed in milliseconds. It typically is the time since the last server reset. Timestamp values wrap around (after about 49.7 days). The server, given its current time is represented by timestamp T, always interprets timestamps from clients by treating half of the timestamp space as being later in time than T. One timestamp value, named CurrentTime, is never generated by the server. This value is reserved for use in requests to represent the current server time." via: https://www.x.org/releases/X11R7.7/doc/libX11/libX11/libX11.html#Pointer_Grabbing So it looks like maybe the X11 folks already handle the timestamp rollover case, and kwin is being too clever? -- You are receiving this mail because: You are watching all bug changes.
