Application: kwin (4.6.2 (4.6.2)) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.2 Operating System: Linux 3.0.0-0300-generic x86_64 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: Ran kwin with desktop effects off, then turned them on. Done from a console - output below: kwin --replace OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop OpenGL version string: 1.4 (2.1 Mesa 7.12-devel) Driver: Intel GPU class: i965 OpenGL version: 1.4 Mesa version: 7.12 X server version: 1.10.2 Linux kernel version: 3.0 Direct rendering: no Requires strict binding: yes GLSL shaders: no Texture NPOT support: yes kwin(5745): glCheckFramebufferStatus failed: "GL_NO_ERROR" Application::crashHandler() called with signal 11; recent crashes: 1 OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop OpenGL version string: 1.4 (2.1 Mesa 7.12-devel) Driver: Intel GPU class: i965 OpenGL version: 1.4 Mesa version: 7.12 X server version: 1.10.2 Linux kernel version: 3.0 Direct rendering: no Requires strict binding: yes GLSL shaders: no Texture NPOT support: yes KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/adrian/.kde/socket-avalon/kdeinit4__0 kwin(5752): glCheckFramebufferStatus failed: "GL_NO_ERROR" Application::crashHandler() called with signal 11; recent crashes: 2 KCrash: Application 'kwin' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/adrian/.kde/socket-avalon/kdeinit4__0 The fact that it mentions the Intel driver makes me wonder if this is actually separate from the other possibly related bugs, or if those other ones weren't really due to misconfiguration after all. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault [KCrash Handler] #6 memcpy () at ../sysdeps/x86_64/memcpy.S:267 #7 0x00007f73a054d410 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 #8 0x00007f738a6f326a in KWin::ARBBlurShader::init (this=0x13a55c0) at ../../../kwin/effects/blur/blurshader.cpp:473 #9 0x00007f738a6f0072 in KWin::BlurEffect::reconfigure (this=0x13a7b10, flags=<value optimized out>) at ../../../kwin/effects/blur/blur.cpp:76 #10 0x00007f738a6f01d7 in KWin::BlurEffect::BlurEffect (this=0x13a7b10) at ../../../kwin/effects/blur/blur.cpp:48 #11 0x00007f738a6f0286 in KWin::effect_create_kwin4_effect_blur () at ../../../kwin/effects/blur/blur.cpp:29 #12 0x00007f73a30411eb in KWin::EffectsHandlerImpl::loadEffect (this=0x1324490, name=...) at ../../kwin/effects.cpp:1128 #13 0x00007f73a30423d1 in KWin::EffectsHandlerImpl::reconfigure (this=0x1324490) at ../../kwin/effects.cpp:143 #14 0x00007f73a301d04c in KWin::Workspace::setupCompositing (this=0x7f7384008d60) at ../../kwin/composite.cpp:216 #15 0x00007f73a2fa2deb in KWin::Workspace::Workspace (this=0x7f7384008d60, restore=false) at ../../kwin/workspace.cpp:222 #16 0x00007f73a2fba38c in KWin::Application::Application (this=<value optimized out>) at ../../kwin/main.cpp:330 #17 0x00007f73a2fbbe7d in kdemain (argc=<value optimized out>, argv=0x7fff6f99f918) at ../../kwin/main.cpp:516 #18 0x00007f73a2bedeff in __libc_start_main (main=0x400740 <main(int, char**)>, argc=3, ubp_av=0x7fff6f99f918, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff6f99f908) at libc-start.c:226 #19 0x0000000000400669 in _start () This bug may be a duplicate of or related to bug 270818. Possible duplicates by query: bug 278741, bug 277528, bug 275325, bug 274090, bug 273694. Reported using DrKonqi
An addition to the above - given the crash happened in a blur shader I tried switching off the Blur effect (blue background of semitransparent windows) and this works around the problem perfectly. I've quickly tried the other available effects and although there are a couple that flatly refuse to start none of the others cause kwin to crash, so it looks like there is a real bug there.
The blur effect is the only one that calls glGenProgramsARB() which causes all those crashes. They all (probably, at least all with complete traces) walk through __indirect_glProgramParameters4fvNV and end up in memcpy what's a bit too reproducable to be a general memory corruption in kwin but is rather a mesa issue?! Ensure to enable direct rendering in "kcmshell4 kwincompositing", "advanced" tab and to NOT have LIBGL_ALWAYS_INDIRECT=1 exported - The line in the kwin output should say: Direct rendering: yes *** This bug has been marked as a duplicate of bug 270818 ***