I'm not sure whether this is a KDE4 issue, a Hardy Heron issue, a Compiz issue, or maybe just an OOO issue. (Or, maybe it's a dibl issue ........ 
)
OK, try this --- with Compiz enabled, open your KDE4 D3lphin, browse to an Open Office text document (the example happens to be a 4-page .rtf format document), and click it to open it. What do you observe during the next 2 minutes?
Here, the OOO splash (still Ubuntu orange, btw) opens, and then the document opens and displays correctly. On my gkrellm monitor, I see both CPU cores go to 98% - 100%, hear the CPU fan speed up, and the system grinds to a near freeze. I can't imagine dealing with it on hardware any slower than mine, which is pretty fast.
First, I closed the browser and other windows. Then I closed the document and D3lphin, but the OOO splash screen remains on the screen -- it was underneath the document. CPU cores are still sitting there at 100% and 66 degrees C.
Then, exercising more patience than I actually have, clicking once every 3 minutes, I get the KDE4 System Monitor open, and observe that the process "oosplash.bin" is using 35% of the resources, and "compiz-real" is using the rest of them. Compiz typically uses only 1% - 2%. So, I manage to kill "oosplash.bin". Instant relief! The CPU cores drop to 2% each, compiz-real is back to 1%, and everything works like it's supposed to.
Launchpad shows no bugs reported for oosplash.bin -- I don't want to start filing bugs until I can hear from others about this.
)OK, try this --- with Compiz enabled, open your KDE4 D3lphin, browse to an Open Office text document (the example happens to be a 4-page .rtf format document), and click it to open it. What do you observe during the next 2 minutes?
Here, the OOO splash (still Ubuntu orange, btw) opens, and then the document opens and displays correctly. On my gkrellm monitor, I see both CPU cores go to 98% - 100%, hear the CPU fan speed up, and the system grinds to a near freeze. I can't imagine dealing with it on hardware any slower than mine, which is pretty fast.
First, I closed the browser and other windows. Then I closed the document and D3lphin, but the OOO splash screen remains on the screen -- it was underneath the document. CPU cores are still sitting there at 100% and 66 degrees C.
Then, exercising more patience than I actually have, clicking once every 3 minutes, I get the KDE4 System Monitor open, and observe that the process "oosplash.bin" is using 35% of the resources, and "compiz-real" is using the rest of them. Compiz typically uses only 1% - 2%. So, I manage to kill "oosplash.bin". Instant relief! The CPU cores drop to 2% each, compiz-real is back to 1%, and everything works like it's supposed to.
Launchpad shows no bugs reported for oosplash.bin -- I don't want to start filing bugs until I can hear from others about this.
)
Comment