Application: knights (2.4.0) KDE Platform Version: 4.7.4 (4.7.4) "release 5" Qt Version: 4.7.4 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Looking at the ‘About’ window while the clock counted down to zero (causing me to lose). -- Backtrace: Application: Springarar (knights), signal: Segmentation fault [Current thread is 1 (Thread 0x7ffe0a5aa7a0 (LWP 10557))] Thread 2 (Thread 0x7ffde2f86700 (LWP 10766)): #0 0x00007ffe0698e523 in poll () from /lib64/libc.so.6 #1 0x00007ffdff0cca98 in g_main_context_poll (n_fds=1, fds=0x7ffdd00013e0, timeout=-1, context=0x7ffdd00009d0, priority=<optimized out>) at gmain.c:3386 #2 g_main_context_iterate (context=0x7ffdd00009d0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3068 #3 0x00007ffdff0ccf59 in g_main_context_iteration (context=0x7ffdd00009d0, may_block=1) at gmain.c:3136 #4 0x00007ffe08252576 in QEventDispatcherGlib::processEvents (this=0x7ffdd00008e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #5 0x00007ffe08226a22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007ffe08226c1f in QEventLoop::exec (this=0x7ffde2f85d20, flags=...) at kernel/qeventloop.cpp:201 #7 0x00007ffe0813e5df in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #8 0x00007ffe08141025 in QThreadPrivate::start (arg=0x2f8da80) at thread/qthread_unix.cpp:331 #9 0x00007ffdfb6d725a in ?? () from /usr/lib64/libGL.so.1 #10 0x00007ffe04d6df05 in start_thread (arg=0x7ffde2f86700) at pthread_create.c:301 #11 0x00007ffe0699763d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ffe0a5aa7a0 (LWP 10557)): [KCrash Handler] #6 0x0000000000000020 in ?? () #7 0x000000000044d85d in Knights::MainWindow::fileNew (this=0x9172f0) at /usr/src/debug/knights-2.4.0/src/knights.cpp:181 #8 0x000000000045122c in Knights::MainWindow::qt_metacall (this=0x9172f0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x2514130) at /usr/src/debug/knights-2.4.0/build/src/knights.moc:89 #9 0x00007ffe0823e14a in QObject::event (this=0x9172f0, e=<optimized out>) at kernel/qobject.cpp:1226 #10 0x00007ffe073ced4b in QWidget::event (this=0x9172f0, event=0x1c9eae0) at kernel/qwidget.cpp:8754 #11 0x00007ffe0778d04b in QMainWindow::event (this=0x9172f0, event=0x1c9eae0) at widgets/qmainwindow.cpp:1478 #12 0x00007ffe0a0b0d48 in KXmlGuiWindow::event (this=0x9172f0, ev=0x1c9eae0) at /usr/src/debug/kdelibs-4.7.4/kdeui/xmlgui/kxmlguiwindow.cpp:126 #13 0x00007ffe0737ec34 in notify_helper (e=0x1c9eae0, receiver=0x9172f0, this=0x6ea090) at kernel/qapplication.cpp:4481 #14 QApplicationPrivate::notify_helper (this=0x6ea090, receiver=0x9172f0, e=0x1c9eae0) at kernel/qapplication.cpp:4453 #15 0x00007ffe07383ac1 in QApplication::notify (this=0x7fff834a27d0, receiver=0x9172f0, e=0x1c9eae0) at kernel/qapplication.cpp:4360 #16 0x00007ffe09fb4186 in KApplication::notify (this=0x7fff834a27d0, receiver=0x9172f0, event=0x1c9eae0) at /usr/src/debug/kdelibs-4.7.4/kdeui/kernel/kapplication.cpp:311 #17 0x00007ffe0822781c in QCoreApplication::notifyInternal (this=0x7fff834a27d0, receiver=0x9172f0, event=0x1c9eae0) at kernel/qcoreapplication.cpp:787 #18 0x00007ffe0822abf8 in sendEvent (event=0x1c9eae0, receiver=0x9172f0) at kernel/qcoreapplication.h:215 #19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x676a70) at kernel/qcoreapplication.cpp:1428 #20 0x00007ffe082520b3 in sendPostedEvents () at kernel/qcoreapplication.h:220 #21 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277 #22 0x00007ffdff0cc58d in g_main_dispatch (context=0x6ec920) at gmain.c:2425 #23 g_main_context_dispatch (context=0x6ec920) at gmain.c:2995 #24 0x00007ffdff0ccd88 in g_main_context_iterate (context=0x6ec920, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073 #25 0x00007ffdff0ccf59 in g_main_context_iteration (context=0x6ec920, may_block=1) at gmain.c:3136 #26 0x00007ffe0825250f in QEventDispatcherGlib::processEvents (this=0x676280, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #27 0x00007ffe07421f9e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #28 0x00007ffe08226a22 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #29 0x00007ffe08226c1f in QEventLoop::exec (this=0x7fff834a2760, flags=...) at kernel/qeventloop.cpp:201 #30 0x00007ffe0822ade7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #31 0x0000000000418177 in main (argc=1, argv=0x7fff834a2b68) at /usr/src/debug/knights-2.4.0/src/main.cpp:87 Reported using DrKonqi
That's interesting, it doesn't crash for me (Qt 4.8, KDE 4.7). Instead, I can start the new game, but if I choose 'New', the board display stop responding. If I choose 'Cancel' and then start a new game from the menu, everything works. Showing multiple dialog simultaneously is a very bad thing, but I really don't know what to do in the case you describe. Normally, games can pause while showing all kinds of dialogs or saving files, but I can't do that when playing on a server.
Not reproducable anymore with Qt5 and kf5.