Hi,
Recently I've installed kubuntu 9.10, I have a ATI hd5770.


Compositing is marked as temporarily disabled in Desktop
Effects on every login. Clicking on "Resume Compositing" brings up the
following error:

The KDE Window Manager: Compositing has been suspended by another application.
You can resume using the Alt+Shift+F12 shortcut.

Clicking on Resume Compositing again, does enable compositing and it works
well.

Could you help me please?
Many thanks and sorry for my english!

Which applications do you have configured to start on login?

bcooksley wrote:Which applications do you have configured to start on login?

Hi again,
I think that I dont have nothing:

david@kubuntu:~/.kde/Autostart$ ls -tlr
total 0

Thanks

Can you please check under ~/.config/autostart also?

bcooksley wrote:Can you please check under ~/.config/autostart also?

Nothing
david@kubuntu:~/.config/autostart$ ls -ltr
total 0

Can you please check to ensure that nothing which uses 3D is enabled in System Settings > Advanced > Autostart?

bcooksley wrote:Can you please check to ensure that nothing which uses 3D is enabled in System Settings > Advanced > Autostart?

I see : gtk2-engines-qtcurve.rc.sh : enabled.

Can you reproduce this under a new user?

If you can reproduce it, then this is an issue with your distribution.
If you cannot, then it is probable the offending application is being resumed with your session.

bcooksley wrote:Can you reproduce this under a new user?

If you can reproduce it, then this is an issue with your distribution.
If you cannot, then it is probable the offending application is being resumed with your session.

Many thanks.
With other user happens the same.
I've solved the problem checking the option: Disable check functionality

Many thanks,

Can you please file a bug at bugs.kde.org regarding this? KWin shouldn't enable compositing at all if the functionality checks fail, which probably means a check is causing high load in your driver during the startup procedure.

bcooksley wrote:Can you please file a bug at bugs.kde.org regarding this? KWin shouldn't enable compositing at all if the functionality checks fail, which probably means a check is causing high load in your driver during the startup procedure.

The checks at startup only do a visibility test to see if compositing works. It seems that some drivers have problems during the startup, so the functionality check passes, but Compositing get's disabled by the high load during startup.

I don't see any possibility to investigate such an issue on a system where it does not happen