Application: kwin (4.5.4 (KDE 4.5.4) "release 9") KDE Platform Version: 4.5.4 (KDE 4.5.4) "release 9" Qt Version: 4.6.3 Operating System: Linux 2.6.34.7-0.5-desktop i686 Distribution: "openSUSE 11.3 (i586)" -- Information about the crash: - What I was doing when the application crashed: Appl KWin always crashed when change decoration or\and theme. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault [KCrash Handler] #7 0xb6b2627b in dri2DrawableGetMSC (psc=0x8132000, pdraw=0x0, ust=0xbfe04a08, msc=0xbfe04a00, sbc=0xbfe049f8) at dri2_glx.c:226 #8 0xb6aff107 in __glXGetVideoSyncSGI (count=0xbfe04a4c) at glxcmds.c:2317 #9 0xb761f4f4 in KWin::SceneOpenGL::waitSync (this=0x8170410) at /usr/src/debug/kdebase-workspace-4.5.4/kwin/scene_opengl.cpp:796 #10 0xb76363a4 in KWin::SceneOpenGL::flushBuffer (this=0x8170410, mask=32, damage=...) at /usr/src/debug/kdebase-workspace-4.5.4/kwin/scene_opengl.cpp:845 #11 0xb76879f0 in KWin::SceneOpenGL::paint (this=0x8170410, damage=..., toplevels=...) at /usr/src/debug/kdebase-workspace-4.5.4/kwin/scene_opengl.cpp:774 #12 0xb7664954 in KWin::Workspace::performCompositing (this=0x817abb0) at /usr/src/debug/kdebase-workspace-4.5.4/kwin/composite.cpp:454 #13 0xb7697bcb in KWin::Workspace::qt_metacall (this=0x817abb0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfe04d3c) at /usr/src/debug/kdebase-workspace-4.5.4/build/kwin/workspace.moc:583 #14 0xb6699efd in QMetaObject::metacall (object=0x817abb0, cl=QMetaObject::InvokeMetaMethod, idx=190, argv=0xbfe04d3c) at kernel/qmetaobject.cpp:237 #15 0xb66a8fe8 in QMetaObject::activate (sender=0x817ae60, m=0xb67b05a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #16 0xb66f5a35 in QTimer::timeout (this=0x817ae60) at .moc/release-shared/moc_qtimer.cpp:134 #17 0xb66ae8e6 in QTimer::timerEvent (this=0x817ae60, e=0xbfe05290) at kernel/qtimer.cpp:271 #18 0xb66a6774 in QObject::event (this=0x817ae60, e=0xbfe05290) at kernel/qobject.cpp:1212 #19 0xb5bcdc64 in QApplicationPrivate::notify_helper (this=0x8070798, receiver=0x817ae60, e=0xbfe05290) at kernel/qapplication.cpp:4302 #20 0xb5bd5bf7 in QApplication::notify (this=0xbfe055c4, receiver=0x817ae60, e=0xbfe05290) at kernel/qapplication.cpp:3706 #21 0xb719a991 in KApplication::notify (this=0xbfe055c4, receiver=0x817ae60, event=0xbfe05290) at /usr/src/debug/kdelibs-4.5.4/kdeui/kernel/kapplication.cpp:310 #22 0xb75f9bff in KWin::Application::notify (this=0xbfe055c4, o=0x817ae60, e=0xbfe05290) at /usr/src/debug/kdebase-workspace-4.5.4/kwin/main.cpp:372 #23 0xb6693e0e in QCoreApplication::notifyInternal (this=0xbfe055c4, receiver=0x817ae60, event=0xbfe05290) at kernel/qcoreapplication.cpp:726 #24 0xb66c270e in sendEvent (this=0x8070f10) at kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (this=0x8070f10) at kernel/qeventdispatcher_unix.cpp:618 #26 0xb66c2ffd in QEventDispatcherUNIX::processEvents (this=0x8054b08, flags=...) at kernel/qeventdispatcher_unix.cpp:939 #27 0xb5c7ef5a in QEventDispatcherX11::processEvents (this=0x8054b08, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #28 0xb669311d in QEventLoop::processEvents (this=0xbfe05514, flags=...) at kernel/qeventloop.cpp:149 #29 0xb6693319 in QEventLoop::exec (this=0xbfe05514, flags=...) at kernel/qeventloop.cpp:201 #30 0xb6697c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #31 0xb5bcb164 in QApplication::exec () at kernel/qapplication.cpp:3581 #32 0xb769611b in kdemain (argc=3, argv=0xbfe05814) at /usr/src/debug/kdebase-workspace-4.5.4/kwin/main.cpp:531 #33 0x0804860b in main (argc=3, argv=0xbfe05814) at /usr/src/debug/kdebase-workspace-4.5.4/build/kwin/kwin_dummy.cpp:3 This bug may be a duplicate of or related to bug 247408. Possible duplicates by query: bug 259557, bug 258774, bug 257395, bug 256037, bug 253698. Reported using DrKonqi
upstream bug, update mesa or disable vsync'ing (advanced tab) to work around, suspend compositing (shift+alt+f12) around changing _any_ window manager related settings... *** This bug has been marked as a duplicate of bug 241263 ***