Created attachment 59961 [details] Screenshot Version: 1.0 (using KDE 4.6.2) OS: Linux In the Desktop Effects control module I see the notice "Desktop effects are not available on this system due to the following technical issues:" That's all (see screenshot). It doesn't tell me which the issues were. Reproducible: Always Steps to Reproduce: Open Desktop Effects (on my system). Expected Results: I'd expect to see the issues which made KWin disable the Desktop Effects on my system. OS: Linux (x86_64) release 2.6.38-8-generic Compiler: cc GLX version: 1.4 OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RS880 OpenGL version string: 2.1 Mesa 7.10.2 OpenGL shading language version string: 1.20
* When I click Resume Effects I get the Notification "Desktop effects have been suspended by another application. You can resume using the 'Alt+Shift+F12' shortcut" * When I hit Alt-Shift-F12 the Compositing State switches to Enabled. The notice above doesn't disappear though. Doesn't look like I have any more effects afterwards. * When I close the KCM and re-open it, the Compositing State is set to disabled again. * This is KDE 4.6.3 (missing in the bugzilla dropdown).
Interesting. Maybe this is caused by the list on the All Effects tab being empty on my system. This is Kubuntu natty with the KDE 4.6.3 packages form the kubuntu-ppa (cf. <http://www.kubuntu.org/news/kde-release-463>). On my other PC I use the same packages and the list isn't empty. The debug output in xsession-errors gave me a hint I'm now investigating (is the message the one which is supposed to be in the empty notification area this bug is actually about?): OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RS880 OpenGL version string: 2.1 Mesa 7.10.2 OpenGL shading language version string: 1.20 Driver: R600G GPU class: R600 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 7.10.2 X server version: 1.10.1 Linux kernel version: 2.6.38 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes kwin(2105) KWin::Workspace::setupCompositing: KWin has detected that your OpenGL library is unsafe to use, falling back to XRender. kwin(2105): Failed to initialize compositing, compositing disabled kwin(2105): Consult http://techbase.kde.org/Projects/KWin/4.0-release-notes#Setting_up
Fixed in git master. close the dialog, do kwriteconfig --file kwinrc --group Compositing --key CheckIsSafe true kwriteconfig --file kwinrc --group Compositing --key OpenGLIsUnsafe false restart the dialog. Be prepared for kwin or X11 to crash when re-enabling compositing. The key isn't there for no reason. *** This bug has been marked as a duplicate of bug 250865 ***
Jepp, found this after some googling. The following (blacklisted?) device works fine here, no crashes, no trouble: 01:05.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 1475 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at c0000000 (32-bit, prefetchable) [size=256M] I/O ports at 5000 [size=256] Memory at d4300000 (32-bit, non-prefetchable) [size=64K] Memory at d4200000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RS880 OpenGL version string: 2.1 Mesa 7.10.2 OpenGL shading language version string: 1.20 Driver: R600G GPU class: R600 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 7.10.2 X server version: 1.10.1 Linux kernel version: 2.6.38 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes
No blacklist (anymore, never again ;-) The key is local and only means that your copy of kwin once crashed for (likely) an ultra-buggy driver. Once the driver got fixed (or the the GPU was replaced) the key is invalid, but there's no way to know (no, we cannot check for the GPU/driver version - this usually caused the crash :-( It was added then as a quick reaction of self-protection and nobody thought about a way back ;-)
Jepp, I switched notebooks recently and just copied my system over. I think compositing indeed crashed KWin on the old system looong time ago... I never bothered to try again until now. A simple check should be possible here: If it is a completely new GPU (you could check based on the PCI IDs, I don't think you can cause any crashes by doing so), the user could be asked on the first logon on the new machine if it should be rechecked. Anyway, looks like bug 250865 brought us an easy way to re-enable compositing, thats probably enough.
Bulk change: move all KWin kcm bugs to product kwin