drago01 on 01/19/2010 04:28 AM wrote: > No it shouldn't this was an issue with the xserver; an updated xserver > fixed it not the kernel. Ah. I had not rebooted the machines with the X update until 2.6.32 was installed. Good to know.