Created attachment 52876 [details] log files + results of glxinfo Version: unspecified (using KDE 4.5.1) OS: Linux I am not sure I am filing this report at the proper place ; if not please reorganize ; thanks. With new kernel 2.6.35-22-generic boot is chaotic ; no blue screen with Kubuntu en white color ; in some cases it does not go through a proper logging situation hanging with no mouse pointer and no keyboard actif ; when I can log to a kde session impossible to set 3d effects on desktop : the "activate" button on general tab is shadowed. If I log to a Gnome session I have the 3d desktop activated. If I boot with kernel 2.6.32-25-generic boot as expected and logning as well but now I have also lost the 3d effects on desktop ; my graphic card is a hd 4850 radeon and I am using the free radeon driver that until update to Maevrick distro was working fine ; I have attached below some log files ; this time though boot process was not as expected I could log we no problem. Reproducible: Always Steps to Reproduce: boot + kde session Actual Results: kernel 2.6.35-22-generic : chaotic boot, chaotic loggin et if possible to log no 3d effects on desktop whatever kernel used ; if I log to a Gnome session when possible 3d effects are there. Expected Results: typical blue boot screen, normal logging session, 3d effects activated on kde. I have another machine with different BIOS version, same processor and graphic card (hd 4850 not not exactly same version) same kernel : there though boot is normal with blue screen and logging as expected when logging to a kde session 3d effects cannot be set.
For the boot problems, or anything that is wrong before the KDE session is started, please report those to your distribution's bugtracker. For 3D not working within KWin, try disabling the functionality checks in systemsettings (Desktop Effects > Advanced).
@cristoph that won't work (buggy UI) since you cannot activate the tab is you cannot enable compositing... @dmoyne edit ~/.kde/share/config/kwinrc, and ensure the following keys are present and set this way [Compositing] CheckIsSafe=true DisableChecks=true Enabled=true OpenGLIsUnsafe=false then run the config dialog ("kcmshell4 kwincompositing") the general problems might defer from a switch to or bug in kms and once kwin figured your drivers crash kwin it will protect itself by no more attempting to enable compositing (yet you should probably still be allowed to do so...)
answser comment #1 : Desktop Effects > Advanced is not accessible as shadowed answser comment #2 : Since I have filed the bug report I have switched to "fglrx" proprietary driver for radeon hd 4xxx serie video cards ; this time boot and logging processes were neat ; but when logging to a kde session I experienced the same problem : no possibility to set a 3d desktop as all options were shadowed ; however I used in konsole : $ fusion-icon then the use of compiz was fine basically like in a Gnome session. After reading this comment I did not use compiz as described abode but made the suggested corrections to kwinrc ; by doing so setting 3d desktop (without compiz ?) worked fine ; thanks. In parallel I used this method on the "radeon" driver as set on my other computer and it works the same way. The question is what is the best driver : the free driver "radeon" or the proprietary driver "fglrx" not directly linked to kde 3d desktop : for the "gelly" windows for sure 3d effects is much more fluid with proprietary driver.
(In reply to comment #3) > The question is what is the best driver : the free driver "radeon" or the > proprietary driver "fglrx" not directly linked to kde 3d desktop : for the > "gelly" windows for sure 3d effects is much more fluid with proprietary driver. no idea, but my rough guess would be to avoid drivers that cause boot problems (free ati / kms, i assume?!) as long as they're not operative. since ati isn't known to provide longtime support in fglrx, one should have a look at the free driver from time to time though ;-) I'm changing this bug to "kwin config dialog won't let me disable compositing checks", since that one is KDE/kwin & valid
I have reinstalled "radeon" driver and meanwhile updated to KDE 4.5.2 (I think effect of this last update is not relevent here) ; now I am experiencing this : - chaotic boot as before : black screen with kernel 2.6.35-22-generic until the logging window is supposed to pop-up ; sometimes it does but keeps popung-up during keyboard input or keyboard is froozen ; sometimes the logging window does not appera at all I have a scrambled screen. - however if I can log in everything works fine in my kde session : 3d desktop very smooth. So until this bug is sourced and corrected I plan : (1) to file a bug on the compatibility kernel 2.6.35-22-generic and free radeon driver but where ? (2) I will go back to "fglrx" driver that allows my machine to boot and log as expected. Thanks for your help.
xorg/ati -> https://bugs.freedesktop.org/ linux -> https://bugzilla.kernel.org/ but i think everything that troubles you (radeon driver + kms) should be handled in the fdo bugtracker, ask there whether you've to do a kernel bug report
After a change of driver (radeon ATI free driver to fglrx ATI proprietary driver) I had to manually do : [Compositing] ... OpenGLIsUnsafe=false by editing ~/.kde/share/config/kwinrc as this line was : OpenGLIsUnsafe=true
problem was caused by driver crashes and KWin prevents to use compositing when the driver is broken - this is intended. Also that there is no GUI option to enable it again.