first just look in gSystemMonitor
CPU should be like 98% idle
if it's not which process it using it up??
and go from there
then i think look in x and service and kernel log files
this stuff can be different places and called different things
mine are in /var/log
it's hard to know ahead of time what to look for
you can post log files somewhere and have us look if you like
i'd look for stuff like
(this was from my service log once when i had a race condition and it repeated over and over for pages and pages on end until i fixed it when i started kde)
Code:
04/4/14@08:43:41: FAIL: sgi_fam address from=<no address>
04/4/14@08:43:41: START: sgi_fam pid=348 from=<no address>
04/4/14@08:43:41: FAIL: sgi_fam address from=<no address>
04/4/14@08:43:41: START: sgi_fam pid=349 from=<no address
i get this one in my kernel log when i startx but it only repeats a few times then stops
Code:
Apr 13 09:04:34 sourcery kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Apr 13 09:04:34 sourcery kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Apr 13 09:04:34 sourcery kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Apr 13 09:04:34 sourcery kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
basically repeating errors
some logs will just file something like above error repeated 87 times or something.
i think i'd also look at ram used in gnome like -- try changing the background image over and over
while checking x memory usage in gSystemMonitor and make sure it's not going up and up and up.
