Application: kwin (4.6.00 (4.6.0) "release 381") KDE Platform Version: 4.6.00 (4.6.0) "release 381" Qt Version: 4.7.1 Operating System: Linux 2.6.34.7-0.7-desktop x86_64 Distribution: "openSUSE 11.3 (x86_64)" -- Information about the crash: - What I was doing when the application crashed:I was changing desktop effects with KDE 4.6 System Settings. In fact whenever I press the apply it seems things go wrong I haven't tried the Xrenderer -- Backtrace: Application: KWin (kwin), signal: Segmentation fault [Current thread is 1 (Thread 0x7f2a1becf760 (LWP 7559))] Thread 2 (Thread 0x7f29ff3a1710 (LWP 7583)): #0 0x00007f2a1778139c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2a1a59b634 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f2a1a8bd180) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00007f2a1a59b669 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f2a1a8cb254) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00007f2a1777ca4f in start_thread () from /lib64/libpthread.so.0 #4 0x00007f2a1b73b82d in clone () from /lib64/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f2a1becf760 (LWP 7559)): [KCrash Handler] #6 dri2DrawableGetMSC (psc=0x731140, pdraw=0x0, ust=0x7fffbe742a58, msc=0x7fffbe742a50, sbc=0x7fffbe742a48) at dri2_glx.c:226 #7 0x00007f2a18f9e185 in __glXGetVideoSyncSGI (count=0x7fffbe742a9c) at glxcmds.c:2317 #8 0x00007f2a1ba991e1 in KWin::SceneOpenGL::waitSync (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/scene_opengl.cpp:810 #9 0x00007f2a1ba9fda5 in KWin::SceneOpenGL::flushBuffer (this=0xb17fa0, mask=<value optimized out>, damage=...) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/scene_opengl.cpp:822 #10 0x00007f2a1baa0573 in KWin::SceneOpenGL::paint (this=0xb17fa0, damage=..., toplevels=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/scene_opengl.cpp:789 #11 0x00007f2a1ba8866a in KWin::Workspace::performCompositing (this=0x732760) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/composite.cpp:442 #12 0x00007f2a17b0a999 in QObject::event (this=0x732760, e=<value optimized out>) at kernel/qobject.cpp:1175 #13 0x00007f2a16c97cd4 in QApplicationPrivate::notify_helper (this=0x635680, receiver=0x732760, e=0x7fffbe743550) at kernel/qapplication.cpp:4445 #14 0x00007f2a16ca01ca in QApplication::notify (this=<value optimized out>, receiver=0x732760, e=0x7fffbe743550) at kernel/qapplication.cpp:4324 #15 0x00007f2a1b1afec6 in KApplication::notify (this=0x7fffbe743a30, receiver=0x732760, event=0x7fffbe743550) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311 #16 0x00007f2a17af6e2c in QCoreApplication::notifyInternal (this=0x7fffbe743a30, receiver=0x732760, event=0x7fffbe743550) at kernel/qcoreapplication.cpp:732 #17 0x00007f2a17b24658 in sendEvent (this=0x636090) at kernel/qcoreapplication.h:215 #18 QTimerInfoList::activateTimers (this=0x636090) at kernel/qeventdispatcher_unix.cpp:618 #19 0x00007f2a17b24d40 in QEventDispatcherUNIX::processEvents (this=0x612380, flags=...) at kernel/qeventdispatcher_unix.cpp:937 #20 0x00007f2a16d3dccc in QEventDispatcherX11::processEvents (this=0x612380, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #21 0x00007f2a17af6262 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #22 0x00007f2a17af6475 in QEventLoop::exec (this=0x7fffbe743920, flags=...) at kernel/qeventloop.cpp:201 #23 0x00007f2a17afa8db in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #24 0x00007f2a1ba26caa in kdemain (argc=<value optimized out>, argv=0x7fffbe743a90) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/main.cpp:542 #25 0x00007f2a1b689b7d in __libc_start_main () from /lib64/libc.so.6 #26 0x0000000000400699 in _start () at ../sysdeps/x86_64/elf/start.S:113 This bug may be a duplicate of or related to bug 241263. Possible duplicates by query: bug 265351, bug 265174, bug 263190, bug 260952, bug 259557. Reported using DrKonqi
driver bug, try to upgrade mesa, but turning off v'Sync should bypass at least this one. *** This bug has been marked as a duplicate of bug 241263 ***