Application that crashed: kwin Version of the application: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) Qt Version: 4.5.2 Operating System: Linux 2.6.29-gentoo-r5 x86_64 What I was doing when the application crashed: Playing konquest made the screen go all funky - the screen would go black, and quickly repaint large portions, but not all, and often even repeating this quickly. Changing desktops and back often got it to stop, but then when I ended my turn, the whole thing would start all over again. And then I got this crash. I'm not sure if it was caused because I was having trouble with the repaint problem and thus moved the window (thus hitting two bugs), or it was just caused by the repaint problem. -- Backtrace: Application: KWin (kwin), signal: Aborted [KCrash Handler] #5 0x00007f2a2729c205 in raise () from /lib/libc.so.6 #6 0x00007f2a2729d723 in abort () from /lib/libc.so.6 #7 0x00007f2a2ae375a5 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2042 #8 0x00007f2a2ae376d0 in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2241 #9 0x00007f2a2cd0a693 in KWin::Workspace::setClientIsMoving (this=0x1cdbfe0, c=0x206c3b0) at /var/tmp/portage/kde-base/kwin-4.2.95/work/kwin-4.2.95/kwin/geometry.cpp:758 #10 0x00007f2a2cd10c39 in KWin::Client::startMoveResize (this=0x206c3b0) at /var/tmp/portage/kde-base/kwin-4.2.95/work/kwin-4.2.95/kwin/geometry.cpp:2693 #11 0x00007f2a2cd13bfc in KWin::Client::handleMoveResize (this=0x206c3b0, x=576, y=25, x_root=2471, y_root=0) at /var/tmp/portage/kde-base/kwin-4.2.95/work/kwin-4.2.95/kwin/geometry.cpp:2845 #12 0x00007f2a2ccebb0e in KWin::Client::motionNotifyEvent (this=0x206c3b0, w=20993727, x=576, y=25, x_root=2471, y_root=0) at /var/tmp/portage/kde-base/kwin-4.2.95/work/kwin-4.2.95/kwin/events.cpp:1433 #13 0x00007f2a2ccec730 in KWin::Client::eventFilter (this=0x206c3b0, o=<value optimized out>, e=0x7fff35196b00) at /var/tmp/portage/kde-base/kwin-4.2.95/work/kwin-4.2.95/kwin/events.cpp:1147 #14 0x00007f2a2af5b9c7 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x22bc3d0, event=0x7fff35196b00) at kernel/qcoreapplication.cpp:726 #15 0x00007f2a2a152bfc in QApplicationPrivate::notify_helper (this=0x1beac30, receiver=0x22bc3d0, e=0x7fff35196b00) at kernel/qapplication.cpp:4052 #16 0x00007f2a2a155b1d in QApplication::notify (this=<value optimized out>, receiver=0x22bc3d0, e=0x7fff35196b00) at kernel/qapplication.cpp:3758 #17 0x00007f2a2bd830b0 in KApplication::notify (this=0x7fff35198a00, receiver=0x22bc3d0, event=0x7fff35196b00) at /var/tmp/portage/kde-base/kdelibs-4.2.95/work/kdelibs-4.2.95/kdeui/kernel/kapplication.cpp:302 #18 0x00007f2a2af5bc6b in QCoreApplication::notifyInternal (this=0x7fff35198a00, receiver=0x22bc3d0, event=0x7fff35196b00) at kernel/qcoreapplication.cpp:606 #19 0x00007f2a2a157729 in QApplicationPrivate::sendMouseEvent (receiver=0x22bc3d0, event=0x7fff35196b00, alienWidget=0x0, nativeWidget=0x22bc3d0, buttonDown=<value optimized out>, lastMouseReceiver=@0x7f2a2abc0fd0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #20 0x00007f2a2a1d134b in QETWidget::translateMouseEvent (this=0x22bc3d0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4409 #21 0x00007f2a2a1cf805 in QApplication::x11ProcessEvent (this=0x7fff35198a00, event=0x7fff351985f0) at kernel/qapplication_x11.cpp:3550 #22 0x00007f2a2a1f8efc in x11EventSourceDispatch (s=0x1bee5d0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #23 0x00007f2a231523d4 in g_main_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x00007f2a23154165 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #25 0x00007f2a2315433d in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x00007f2a2af8ae4f in QEventDispatcherGlib::processEvents (this=0x1bd1470, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #27 0x00007f2a2a1f8648 in QGuiEventDispatcherGlib::processEvents (this=0x1c4f, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #28 0x00007f2a2af5a972 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 890865904}) at kernel/qeventloop.cpp:149 #29 0x00007f2a2af5add6 in QEventLoop::exec (this=0x7fff35198940, flags={i = 890866000}) at kernel/qeventloop.cpp:197 #30 0x00007f2a2af5f39e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #31 0x00007f2a2ccdab9d in kdemain (argc=3, argv=0x7fff35198ee8) at /var/tmp/portage/kde-base/kwin-4.2.95/work/kwin-4.2.95/kwin/main.cpp:527 #32 0x00007f2a272885c6 in __libc_start_main () from /lib/libc.so.6 #33 0x0000000000400949 in _start () Reported using DrKonqi
*** Bug 199019 has been marked as a duplicate of this bug. ***
According to the source code comment it was caused by the moving of the window. Another window was beeing moved at the same time and kwin asserted. I have no idea how this could happen or how to get into such a situation. So without a proper way to reproduce there is no way to fix it :-(
(In reply to comment #2) > I have no idea how this could happen "QEventDispatcherGlib::processEvents" A release event was probably lost, given the circumstances* and that events sometimes get delayed in this dispatcher (i have /no/ idea why t would use it as default) this sounds resonable... (but could be more down in X11 or the input driver - i however doubt so) @Darin how is the situation about this issue? doe konquest work or do you run into similar situations otherwise? *"screen go all funky - the screen would go black, and quickly repaint large portions, but not all, and often even repeating this quickly. Changing desktops and back often got it to stop" - sounds like a fully loaded system...
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
It's highly unlikely the system was overloaded at the time. However, in the intervening years, between 2009 and 2011, or 2011 and 2018 (now), pretty much everything has changed. The KDE versions are all different, the video drivers are improved, X has upgraded, and many other changes. Heck, I've upgraded hardware more than once. The net result is that I'm not having this issue now, so I'm not really able to provide more information than is already attached. It seems like it's fixed, but whether that was Konquest, Kwin, X, or nvidia drivers, I can't really be sure.
Ok, I'll close this out then. If it occurs again, please feel free to submit again. Thank you for the update!