0dc2bb6101
The timestamp transferred in the X protocol is a 32-bit number of milliseconds. The timestamp stored in the server is a structure that contains two fields: months (!) and milliseconds. When the server passes the config timestamp to the client, it discards the months part and sends only the milliseconds part. When the server receives the config timestamp from the client, it tries to guess the "months" part by looking at the current time and then maybe adding or subtracting one. The guess is wrong after the server has been running long enough (several hours). I have added two ErrorF calls around the 'if' statement that returns RRSetConfigInvalidConfigTimestamp in randr/randr.c and my Xorg.0.log has this: randr request got good config time: 0:-2103495671 for the first few successful xrandr calls, and randr request failed with RRSetConfigInvalidConfigTime: client passed 1:-2103495671, server has 0:-2103495671 when it fails. The server has been running for 8 and a half hours. The obvious fix would be to ignore the months field and only compare the milliseconds. |
||
|---|---|---|
| .. | ||
| Makefile.am | ||
| mirandr.c | ||
| randr.c | ||
| randrstr.h | ||
| rrcrtc.c | ||
| rrdispatch.c | ||
| rrinfo.c | ||
| rrmode.c | ||
| rroutput.c | ||
| rrpointer.c | ||
| rrproperty.c | ||
| rrscreen.c | ||
| rrsdispatch.c | ||
| rrxinerama.c | ||