Application: kwin (4.10.5 "release 1") KDE Platform Version: 4.10.5 "release 1" Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.16-desktop x86_64 Distribution: "openSUSE 12.3 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: just playing openarena-x64, then a wine-game(win32-exe), then again openarena (opengl). after quit oa kwin gives crash-msg - Unusual behavior I noticed: after boot(restart)/login a kscreensaver-window appears/remains on desktop every login although no screensaver was active while shutdown. maybe another topic, but this behavior i noticed since time of installation... -- Backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e6ba367c0 (LWP 2584))] Thread 2 (Thread 0x7f5e4d894700 (LWP 2594)): #0 0x00007f5e661e2964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f5e67b31307 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f5e67e3e660 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00007f5e67b31339 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00007f5e661dee0f in start_thread () from /lib64/libpthread.so.0 #4 0x00007f5e6b2557dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5e6ba367c0 (LWP 2584)): [KCrash Handler] #6 QMetaObject::invokeMethod (obj=0x36100000000, member=<optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166 #7 0x00007f5e69a23a70 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7f5e69a32002 "addLayerRepaint", obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:434 #8 KWin::EffectWindow::addLayerRepaint (this=<optimized out>, r=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwineffects.cpp:793 #9 0x00007f5e69a2f88d in KWin::AnimationEffect::postPaintScreen (this=<optimized out>) at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinanimationeffect.cpp:543 #10 0x00007f5e6b5f3cf8 in KWin::EffectsHandlerImpl::postPaintScreen (this=0x269a1b0) at /usr/src/debug/kde-workspace-4.10.5/kwin/effects.cpp:260 #11 0x00007f5e6b5d4095 in KWin::Scene::paintScreen (this=0x25f77b0, mask=<optimized out>, region=0x7fffa2cb77e0) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:144 #12 0x00007f5e6b5da6dc in KWin::SceneXrender::paint (this=0x25f77b0, damage=..., toplevels=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_xrender.cpp:187 #13 0x00007f5e6b5ce36c in KWin::Compositor::performCompositing (this=0x25cd540) at /usr/src/debug/kde-workspace-4.10.5/kwin/composite.cpp:610 #14 0x00007f5e665855ac in QObject::event (this=0x25cd540, e=<optimized out>) at kernel/qobject.cpp:1165 #15 0x00007f5e656fe86c in QApplicationPrivate::notify_helper (this=this@entry=0x23b4380, receiver=receiver@entry=0x25cd540, e=e@entry=0x7fffa2cb7fc0) at kernel/qapplication.cpp:4562 #16 0x00007f5e65702ceb in QApplication::notify (this=0x7fffa2cb8600, receiver=0x25cd540, e=0x7fffa2cb7fc0) at kernel/qapplication.cpp:4423 #17 0x00007f5e6ad4e7f6 in KApplication::notify (this=0x7fffa2cb8600, receiver=0x25cd540, event=0x7fffa2cb7fc0) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311 #18 0x00007f5e66570d8e in QCoreApplication::notifyInternal (this=0x7fffa2cb8600, receiver=0x25cd540, event=0x7fffa2cb7fc0) at kernel/qcoreapplication.cpp:946 #19 0x00007f5e665a1b61 in sendEvent (event=0x7fffa2cb7fc0, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #20 QTimerInfoList::activateTimers (this=0x23b4d78) at kernel/qeventdispatcher_unix.cpp:637 #21 0x00007f5e665a21a0 in QEventDispatcherUNIX::activateTimers (this=this@entry=0x230ea70) at kernel/qeventdispatcher_unix.cpp:894 #22 0x00007f5e665a22f8 in QEventDispatcherUNIX::processEvents (this=0x230ea70, flags=...) at kernel/qeventdispatcher_unix.cpp:956 #23 0x00007f5e6579fa3f in QEventDispatcherX11::processEvents (this=0x230ea70, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #24 0x00007f5e6656fadf in QEventLoop::processEvents (this=this@entry=0x7fffa2cb8310, flags=...) at kernel/qeventloop.cpp:149 #25 0x00007f5e6656fd68 in QEventLoop::exec (this=0x7fffa2cb8310, flags=...) at kernel/qeventloop.cpp:204 #26 0x00007f5e66574a08 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #27 0x00007f5e6b584d9a in kdemain (argc=3, argv=0x7fffa2cb8748) at /usr/src/debug/kde-workspace-4.10.5/kwin/main.cpp:537 #28 0x00007f5e6b18ea15 in __libc_start_main () from /lib64/libc.so.6 #29 0x0000000000400761 in _start () at ../sysdeps/x86_64/start.S:123 Possible duplicates by query: bug 321125. Reported using DrKonqi
please see the dupe and ideally comment on invocation of compositing blocking for the game. the screensaver at login sounds like a (false?) invocation of locked autologin (ie. you're logged in with booting, but the session is protected with the screenlocker) - but that's unrelated (even if it's bug and not configuration) *** This bug has been marked as a duplicate of bug 321125 ***