Steve also asked for some testing with Ubuntu Unity:
- installing an Ubuntu precise desktop with unity7 (which I believe was the
last release using cfq by default) and the .0 kernel (3.2.0)
- using the system for a bit to try to reproduce the original problem -
application windows becoming grayed out by the WM under normal usage,
indicating that the app is not responding
- changing the scheduler to deadline and testing to see if the problem
persists or resolves itself
- upgrading to the trusty backport kernel (linux-image-generic-lts-trusty)
- verifying that the desktop behaves correctly with the default deadline
scheduler
- changing the scheduler to cfq and testing whether the original problem
recurs
although I feel this should be done by the Ubuntu Unity team, there's no reason why Kubuntu should have to spend resources on the fallout from their bugs
Steve also asked for some testing with Ubuntu Unity:
- installing an Ubuntu precise desktop with unity7 (which I believe was the image-generic- lts-trusty)
last release using cfq by default) and the .0 kernel (3.2.0)
- using the system for a bit to try to reproduce the original problem -
application windows becoming grayed out by the WM under normal usage,
indicating that the app is not responding
- changing the scheduler to deadline and testing to see if the problem
persists or resolves itself
- upgrading to the trusty backport kernel (linux-
- verifying that the desktop behaves correctly with the default deadline
scheduler
- changing the scheduler to cfq and testing whether the original problem
recurs
although I feel this should be done by the Ubuntu Unity team, there's no reason why Kubuntu should have to spend resources on the fallout from their bugs