| Summary: | Brightness and shadows of windows don't work in system preferences, workspace appearance | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Victor Marin <vms367> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | hugo.pereira.da.costa |
| Priority: | NOR | ||
| Version: | 4.11.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
No windows shadows / brightness in KDE 4.11.
2. No windows bright-shadows nor effects in KDE 4.11 3. No windows bright-shadows nor effects in KDE 4.11 glxinfo Xrender tab Details of desktop effects that couldn't be loaded with Xrender Failed to activate desktop effects with OpenGL |
||
|
Description
Victor Marin
2013-08-30 12:52:08 UTC
Can you post a screenshot ? My suspission is that after the upgrade, you do not have compositing enabled any more, which is why all the shadows are disabled (and the settings ignored). In which case this is likely unrelated with oxygen (and related to either kwin, or your graphics card driver). http://wstaw.org/m/2013/08/30/plasma-desktopCD2962.png (this is how windows appear, here when compositing is disabled) Created attachment 82037 [details]
No windows shadows / brightness in KDE 4.11.
Perhaps, I don't have compositing enabled anymore after upgrading to 4.11; How could I enable it? Also, I not longer have windows transparency effect nor gelatinous windows, etc. Yes, I'm posting a screenshot. Thanks in advance. So compositing indeed. If available, it can usually be enabled with shift+alt+F12 Otherwise, will forward to kwin team. Created attachment 82041 [details]
2. No windows bright-shadows nor effects in KDE 4.11
Created attachment 82042 [details]
3. No windows bright-shadows nor effects in KDE 4.11
Yes, it seems the problem has to do with a compositing error. Going to system preferences --> desktop effects, it shows that it are enabled, but it are not... Marking or unmarking the activation of the desktop effects it does nothing; Also it can't be enabled by using Alt+Shift+F12. If I try to change some effect in all the effects tab, then a yellowish message appears warning that 22 destkop effects couldn't be loaded. Clicking on the details button of such error message, it spawns that due to technical issues it can't be determined all possible causes of the error. I attach 2 more screenshots. reassigning (In reply to comment #7) > Going to system preferences --> desktop effects, it shows that it are > enabled No, it shows to activate them with kwin startup - doesn't matter, though. > desktop effects it does nothing; Also it can't be enabled by using > Alt+Shift+F12. please attach the output of "glxinfo" and in "kcmshell4 kwincompositing", 3rd tab, try to switch to xrender compositing - does that work? Created attachment 82063 [details]
glxinfo
Created attachment 82064 [details]
Xrender tab
Created attachment 82065 [details]
Details of desktop effects that couldn't be loaded with Xrender
Created attachment 82066 [details]
Failed to activate desktop effects with OpenGL
Here I send you the "glxinfo" in a .txt file, and also 2 additional screenshots with the third tab of "kcmshell4 kwincompositing". Choosing Xrender it enables shadows and brightness in windows. Also, it can be adjusted and changed the windows shadows / brightness colors. And it enables transparency effect, too. But, as the screenshot number 5 shows, some effects can't be loaded with Xrender but it need OpenGL, like gelatinous windows. Trying to enable desktop effects with any and all versions of OpenGL it throws the error message that I also send you in respective screenshot. > OpenGL vendor string: Advanced Micro Devices, Inc. > OpenGL renderer string: ATI Radeon HD 3200 Graphics > OpenGL version string: 3.3.11627 Compatibility Profile Context > OpenGL shading language version string: 3.30 "Surprise" See here for a workaround: https://bugs.kde.org/show_bug.cgi?id=323927 Since direct rendering was disabled for being too crashy, don't forget to undo that workaround as soon as we figured what causes that GL error and avoid it. *** This bug has been marked as a duplicate of bug 323527 *** |
