by NotExcessive » Fri Mar 11, 2011 12:59
About a month or so ago, I put KDE 4.6 onto my Acer Aspire 5745G laptop. It had Sabayon 5.3 (64-bit), Compiz, and Gnome on it, and was rock stable. After I put KDE on, I had nothing but dramas - quite often, I couldn't launch an app, move a window, or use the pager - this was because KDE would freeze and not respond for a period of anywhere between 15 and 60 seconds. So I went back to using Gnome.
Well, yesterday I decided to bite the bullet, and wipe the machine and do a fresh install to see if I can get to the bottom of this. I put Sabayon 5.5 on, with KDE4.6 and Compiz. No other window managers.
After I had the machine up and running, the same problems appeared: my auto-hide panel at the top of the screen occasionally didn't show up until maybe a full minute after I pushed the mouse to the top screen edge; I'd click on the menu launcher and nothing would happen for half a minute; I'd click on a window to drag it across the desktop and nothing would move for 40 seconds... things like that.
Of course after the system unfroze, all of my frustrated actions would fly forth at warp speed because the system had buffered everything.
Quite by accident, on this new installation, I'd set the clock in the bottom panel to show the seconds display (the previous installation only showed minutes). That's when I noticed that the time display would frequently freeze (without my doing anything at all on the machine) for the same sorts of periods that had been plaguing me all along. Also, several times a minute, it would skip a couple of seconds (eg from showing 34 to showing 36), and also bunny-hop (eg hang on 18 for a second and a half, then jump to 19 for a fraction of a second before skipping straight to 20 etc.) and then I realised that it had nothing to do with user activity.
All my troubleshooting had been along the lines of seeing if Compiz was the culprit (loose binding, indirect rendering) but after switching Compiz off and having the problems persist under KDE alone, I was back at square one. I tried to find out what was triggering the freeze when I hit the auto-hide panel or moved a window or used the pager... I never twigged that the system was going to freeze no matter what I was doing (or not doing) because in the previous installation, I didn't have a seconds display on the clock to clue me in.
So the question is: what can be causing this? As I've said, you don't need to be doing anything on the machine. As a test, I noted that when the clock froze and I moved the mouse to the top screen edge to activate the auto-hide panel there, the panel didn't show. When the time display resumed, the panel shot out and acted normally.
The machine has an nvidia GPU, it has the latest nvidia drivers installed, and opengl is set correctly to nvidia. I've gone into KDE settings and disabled nepomuk and strigi. When the freeze happens, existing applications work normally (music plays in clementine perfectly fine and the web browser still surfs the net, although I note that as I'm typing this, I'm frequently prevented from typing text until the system unfreezes, whereupon all my keystrokes shoot out of the buffer and zoom across the text box). Compiz still works and I can rotate the cube with the mouse. I've got top running in yakuake and when the freeze happens all I see is X taking up 7% of the CPU, and memory never gets worse than 0.9%.
Can anyone help solve this? I love KDE but this is driving me nuts.
Last edited by
NotExcessive on Sat May 07, 2011 8:25, edited 1 time in total.