Adam,
On 2010-09-22 21:03, Adam Williamson wrote:
On Wed, 2010-09-22 at 20:29 +1000, Philip Rhoades wrote:
>> I agree with Adam - look for processes eating resources. I recommend
>> using htop (a much better top replacement) and iotop (which will let you
>> look for processes that are using the disk heavily).
>
>
> Using top I found it is Xorg - taking up nearly 100% of CPU time . .
>
> Is there some way to find out what it is about Xorg in particular?
Check /var/log/Xorg.0.log for incriminating messages.
I can't see anything obvious - should I send this log to anyone now that
this version as been OK'd already?
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au