Re: [PATCH xserver] dix: Don't update current time in the middle of input event processing

2016-06-01 Thread Keith Packard
Peter Hutterer writes: >> cc: Chase Douglas >> cc: Peter Hutterer >> cc: Adam Jackson >> Signed-off-by: Keith Packard > > Acked-by: Peter Hutterer

Re: [PATCH xserver] dix: Don't update current time in the middle of input event processing

2016-06-01 Thread Peter Hutterer
On Fri, May 27, 2016 at 05:49:52PM -0700, Keith Packard wrote: > In patch 137ac094e7ab8c871f3b36e40ad826ac797f0e26, Adam moved an > expensive call to UpdateCurrentTime out of the main dispatch > loop. That's a good change as the original fix from Chase was a bit > expensive. However, it breaks

Re: [PATCH xserver] dix: Don't update current time in the middle of input event processing

2016-05-30 Thread Keith Packard
Michel Dänzer writes: > Tested-by: Michel Dänzer > > Thank you for restoring sanity to my GNOME session! Just don't ask how long it took to discover where the problem was... -- -keith signature.asc Description: PGP signature

Re: [PATCH xserver] dix: Don't update current time in the middle of input event processing

2016-05-30 Thread Michel Dänzer
On 28.05.2016 09:49, Keith Packard wrote: > In patch 137ac094e7ab8c871f3b36e40ad826ac797f0e26, Adam moved an > expensive call to UpdateCurrentTime out of the main dispatch > loop. That's a good change as the original fix from Chase was a bit > expensive. However, it breaks grab processing and so a

[PATCH xserver] dix: Don't update current time in the middle of input event processing

2016-05-27 Thread Keith Packard
In patch 137ac094e7ab8c871f3b36e40ad826ac797f0e26, Adam moved an expensive call to UpdateCurrentTime out of the main dispatch loop. That's a good change as the original fix from Chase was a bit expensive. However, it breaks grab processing and so a couple of the calls to UpdateCurrenTime need to