Application: kwin (4.10.3) KDE Platform Version: 4.10.3 Qt Version: 4.8.4 Operating System: Linux 3.8.0-23-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: downloading Kentucky Route 0 game from Steam while playing Penguin Command. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffb58c667c0 (LWP 3321))] Thread 3 (Thread 0x7ffb36c28700 (LWP 3330)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ffb54e87e77 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007ffb54e87ea9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007ffb4c214f8e in start_thread (arg=0x7ffb36c28700) at pthread_create.c:311 #4 0x00007ffb58597e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7ffb35882700 (LWP 3331)): #0 0x00007ffb58590233 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007ffb53a274f3 in qt_safe_select (nfds=23, fdread=0x7ffb2c000ac8, fdwrite=0x7ffb2c000d60, fdexcept=0x7ffb2c000ff8, orig_timeout=0x0) at kernel/qcore_unix.cpp:83 #2 0x00007ffb53a2c499 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7ffb2c000910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x00007ffb53a2cc82 in QEventDispatcherUNIX::processEvents (this=0x7ffb2c0008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:937 #4 0x00007ffb539fa38f in QEventLoop::processEvents (this=this@entry=0x7ffb35881d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007ffb539fa618 in QEventLoop::exec (this=this@entry=0x7ffb35881d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007ffb538fc410 in QThread::exec (this=this@entry=0x1dfa300) at thread/qthread.cpp:542 #7 0x00007ffb539dbedf in QInotifyFileSystemWatcherEngine::run (this=0x1dfa300) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007ffb538febec in QThreadPrivate::start (arg=0x1dfa300) at thread/qthread_unix.cpp:338 #9 0x00007ffb4c214f8e in start_thread (arg=0x7ffb35882700) at pthread_create.c:311 #10 0x00007ffb58597e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7ffb58c667c0 (LWP 3321)): [KCrash Handler] #6 0x0000000000000000 in ?? () #7 0x00007ffb53a05c5c in QMetaObject::invokeMethod (obj=0x1d43630, member=member@entry=0x7ffb56d83c3d "addLayerRepaint", type=type@entry=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166 #8 0x00007ffb56d755d0 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7ffb56d83c3d "addLayerRepaint", obj=<optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:434 #9 KWin::EffectWindow::addLayerRepaint (this=<optimized out>, r=...) at ../../../kwin/libkwineffects/kwineffects.cpp:793 #10 0x00007ffb56d814ad in KWin::AnimationEffect::postPaintScreen (this=<optimized out>) at ../../../kwin/libkwineffects/kwinanimationeffect.cpp:543 #11 0x00007ffb5893c878 in KWin::EffectsHandlerImpl::postPaintScreen (this=0x2390aa0) at ../../kwin/effects.cpp:260 #12 0x00007ffb5891d1b5 in KWin::Scene::paintScreen (this=this@entry=0x232b5f0, mask=mask@entry=0x7fff9f70a7d4, region=region@entry=0x7fff9f70a840) at ../../kwin/scene.cpp:144 #13 0x00007ffb5892a20e in KWin::SceneOpenGL::paint (this=this@entry=0x232b5f0, damage=..., toplevels=...) at ../../kwin/scene_opengl.cpp:308 #14 0x00007ffb5892a3b6 in KWin::SceneOpenGL1::paint (this=0x232b5f0, damage=..., windows=...) at ../../kwin/scene_opengl.cpp:636 #15 0x00007ffb58916acc in KWin::Compositor::performCompositing (this=0x1d469b0) at ../../kwin/composite.cpp:610 #16 0x00007ffb53a153ec in QObject::event (this=0x1d469b0, e=<optimized out>) at kernel/qobject.cpp:1156 #17 0x00007ffb52da18ec in QApplicationPrivate::notify_helper (this=this@entry=0x1be0ef0, receiver=receiver@entry=0x1d469b0, e=e@entry=0x7fff9f70aff0) at kernel/qapplication.cpp:4567 #18 0x00007ffb52da425b in QApplication::notify (this=this@entry=0x7fff9f70b630, receiver=receiver@entry=0x1d469b0, e=e@entry=0x7fff9f70aff0) at kernel/qapplication.cpp:4428 #19 0x00007ffb58082af6 in KApplication::notify (this=0x7fff9f70b630, receiver=0x1d469b0, event=0x7fff9f70aff0) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x00007ffb539fb63e in QCoreApplication::notifyInternal (this=0x7fff9f70b630, receiver=0x1d469b0, event=event@entry=0x7fff9f70aff0) at kernel/qcoreapplication.cpp:946 #21 0x00007ffb53a2cb72 in sendEvent (event=0x7fff9f70aff0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QTimerInfoList::activateTimers (this=0x1be1a38) at kernel/qeventdispatcher_unix.cpp:622 #23 0x00007ffb53a2cbd0 in QEventDispatcherUNIX::activateTimers (this=this@entry=0x1b84ad0) at kernel/qeventdispatcher_unix.cpp:879 #24 0x00007ffb53a2cd28 in QEventDispatcherUNIX::processEvents (this=this@entry=0x1b84ad0, flags=...) at kernel/qeventdispatcher_unix.cpp:941 #25 0x00007ffb52e47b9f in QEventDispatcherX11::processEvents (this=0x1b84ad0, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #26 0x00007ffb539fa38f in QEventLoop::processEvents (this=this@entry=0x7fff9f70b340, flags=...) at kernel/qeventloop.cpp:149 #27 0x00007ffb539fa618 in QEventLoop::exec (this=this@entry=0x7fff9f70b340, flags=...) at kernel/qeventloop.cpp:204 #28 0x00007ffb539ffcf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #29 0x00007ffb52d9fffc in QApplication::exec () at kernel/qapplication.cpp:3828 #30 0x00007ffb588ce04a in kdemain (argc=3, argv=0x7fff9f70b778) at ../../kwin/main.cpp:537 #31 0x00007ffb584bfea5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=3, ubp_av=0x7fff9f70b778, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9f70b768) at libc-start.c:260 #32 0x0000000000400701 in _start () Reported using DrKonqi
most likely bug #320562, but the condition sounds odd. do you let the game block the compositor and it eventually restarted that moment?
On 06/14/2013 03:18 AM, Thomas Lübking wrote: > https://bugs.kde.org/show_bug.cgi?id=321125 > > --- Comment #1 from Thomas Lübking <thomas.luebking@gmail.com> --- > most likely bug #320562, but the condition sounds odd. > do you let the game block the compositor and it eventually restarted that > moment? > Not sure about the game block the compositor thing, but I closed out the game. When I restarted it later, it worked fine. Other downloads also worked fine.
Hmm, the only other thing i could imagine is that this was a follow-up crash, ie. kwin crashed for some unknown reason, pot. OpenGL driver related - given the condition, restarted and then lead to this crash (which would usually occur very early) Judging as dupe because of the backtrace - please re-open it it should ever occur with the bugfixing patch applied (atm. 4.11, eventually to be backported to 4.10.5) *** This bug has been marked as a duplicate of bug 320562 ***
*** Bug 323624 has been marked as a duplicate of this bug. ***