Bug 269611

Application: kwin (4.5.1 (KDE 4.5.1))
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-28-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
Happens when enabling opengl compositing with minimal effects enabled (no blur, tried to blacklist lanczos also). Using latest drivers with kubuntu 10.10, tried with default driver and an alternate package from PPA. Version strings:

OpenGL renderer string: Mesa DRI Intel(R) G45/G43 GEM 20100330 DEVELOPMENT 
OpenGL version string: 2.1 Mesa 7.9-devel
2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64 GNU/Linux
xorg-server 2:1.9.0-0ubuntu7.3

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f89f1828780 (LWP 2357))]

Thread 2 (Thread 0x7f89d88bd700 (LWP 2360)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f89d88bcad0 in ?? ()
#2  0x00007fff045ff852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f89f1828780 (LWP 2357)):
[KCrash Handler]
#6  0x00007f89da303855 in ?? () from /usr/lib/dri/i965_dri.so
#7  0x00007f89eee3a114 in ?? () from /usr/lib/mesa/libGL.so.1
#8  0x00007f89f1413567 in KWin::SceneOpenGL::flushBuffer (this=<value optimized out>, mask=0, damage=) at ../../kwin/scene_opengl.cpp:837
#9  0x00007f89f1414497 in KWin::SceneOpenGL::paint (this=0xf0cc30, damage=<value optimized out>, toplevels=<value optimized out>) at ../../kwin/scene_opengl.cpp:767
#10 0x00007f89f13fe2a7 in KWin::Workspace::performCompositing (this=<value optimized out>) at ../../kwin/composite.cpp:454
#11 0x00007f89f137f7dd in KWin::Workspace::qt_metacall (this=0x7f89d400aa20, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff04561ef0) at ./workspace.moc:583
#12 0x00007f89ed96db27 in QMetaObject::activate (sender=0x7f89d400aee8, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3280
#13 0x00007f89ed9678f9 in QObject::event (this=0x7f89d400aee8, e=0x0) at kernel/qobject.cpp:1183
#14 0x00007f89eca9ffdc in QApplicationPrivate::notify_helper (this=0xdd4fb0, receiver=0x7f89d400aee8, e=0x7fff04562640) at kernel/qapplication.cpp:4396
#15 0x00007f89ecaa5aed in QApplication::notify (this=0x7fff04562a30, receiver=0x7f89d400aee8, e=0x7fff04562640) at kernel/qapplication.cpp:4277
#16 0x00007f89f0ba8156 in KApplication::notify (this=0x7fff04562a30, receiver=0x7f89d400aee8, event=0x7fff04562640) at ../../kdeui/kernel/kapplication.cpp:310
#17 0x00007f89ed955cdc in QCoreApplication::notifyInternal (this=0x7fff04562a30, receiver=0x7f89d400aee8, event=0x7fff04562640) at kernel/qcoreapplication.cpp:732
#18 0x00007f89ed9856f2 in sendEvent (this=0xdd59c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0xdd59c0) at kernel/qeventdispatcher_unix.cpp:602
#20 0x00007f89ed98582c in QEventDispatcherUNIX::processEvents (this=0xdb16e0, flags=) at kernel/qeventdispatcher_unix.cpp:923
#21 0x00007f89ecb53c2f in QEventDispatcherX11::processEvents (this=<value optimized out>, flags=) at kernel/qeventdispatcher_x11.cpp:152
#22 0x00007f89ed954a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007f89ed954dec in QEventLoop::exec (this=0x7fff04562970, flags=) at kernel/qeventloop.cpp:201
#24 0x00007f89ed958ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#25 0x00007f89f139bf9d in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kwin/main.cpp:531
#26 0x00007f89f0fe4d8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff04563038) at libc-start.c:226
#27 0x0000000000400669 in _start ()

This bug may be a duplicate of or related to bug 241263.

Possible duplicates by query: bug 268186, bug 266543, bug 266362, bug 266013, bug 265351.

Reported using DrKonqi