Comment 31 for bug 555595

For what it's worth, I haven't had this problem anymore since I replaced the faulty charger for my Dell (I was using the machine with AC power, battery attached but the battery didn't charge). I think the AC/battery problem mixed up CPU speed a bit like described in bug 555315. I think it wasn't ever an actual Intel/graphics problem directly for me, but a CPU slowdown.

Trying to set the CPU speed manually with GNOME CPU speed applet just caused more problems. If you have used it, it's probably better try to reset whatever it did. If you feel like kicking the ondemand scheduler itself, try:
echo 20 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
echo 20 > /sys/devices/system/cpu/cpu1/cpufreq/ondemand/up_threshold

A different bug, but regarding compiz and maybe what Colin and Stavros are after, one slow compiz problem was earlier solved for me by not having "unredirect_fullscreen_windows" selected in compiz (compizconfig-settings-manager application), but it was not the actual slowdown problem of this bug. Please redirect compiz problems to other bugs.

All in all, it's not very clear what this bug is about: compiz, intel, CPU scheduler, faulty hardware... for me it was CPU speed problem with faulty charger, but let's stick to the original reporter's point of view where possible - if he can't confirm the CPU being (all the time) low clocked at the time the problem occurs, which can be seen with powertop application or GNOME applet, then this bug report is about something other than what I experienced and described and I'm in the wrong bug report anyway. Likewise, if you are seeing eg. "one frame per second" kind of _really_ slow compiz problem, it's not what Virgil seems to be experiencing and probably worth of another bug report about compiz settings. You also shouldn't be asking when _this_ bug is going to be fixed, as your problem is not covered in this actual bug report (similar to my problem possibly not being covered).