Application: kpat (3.6) KDE Platform Version: 4.9.2 Qt Version: 4.8.3 Operating System: Linux 3.5.0-18-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: I had just finished a kpatience game, when it crashed immediately after reporting a win. - Unusual behavior I noticed: Before the above, it didn't notice a complete suit (K down to A), until I moved it to another column -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6db7e46780 (LWP 28337))] Thread 2 (Thread 0x7f6db008a700 (LWP 28338)): #0 0x00007f6dbf9e2303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f6dbb98ed84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f6dbb98eea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f6dc110ac16 in QEventDispatcherGlib::processEvents (this=0x7f6da80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f6dc10db2bf in QEventLoop::processEvents (this=this@entry=0x7f6db0089dd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f6dc10db548 in QEventLoop::exec (this=0x7f6db0089dd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f6dc0fdcb10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #7 0x00007f6dc10bb9af in QInotifyFileSystemWatcherEngine::run (this=0x1adac30) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f6dc0fdfaec in QThreadPrivate::start (arg=0x1adac30) at thread/qthread_unix.cpp:338 #9 0x00007f6dbc255e9a in start_thread (arg=0x7f6db008a700) at pthread_create.c:308 #10 0x00007f6dbf9edcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f6db7e46780 (LWP 28337)): [KCrash Handler] #6 Spider::moveFullRunToLeg (this=0x1a03010, pile=0x19cd1e0) at ../../kpat/spider.cpp:365 #7 0x00000000004244c9 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./moc_dealer.cpp:108 #8 DealerScene::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./moc_dealer.cpp:84 #9 0x00007f6dc10f1f5f in QMetaObject::activate (sender=0x1a03010, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #10 0x00007f6dc10f1f5f in QMetaObject::activate (sender=0x1a0c740, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #11 0x00007f6dc10f1f5f in QMetaObject::activate (sender=0x1a0c6f0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #12 0x00007f6dc10f126c in QObject::event (this=0x1a0c6f0, e=<optimized out>) at kernel/qobject.cpp:1157 #13 0x00007f6dc0483e9c in QApplicationPrivate::notify_helper (this=this@entry=0x17f2da0, receiver=receiver@entry=0x1a0c6f0, e=e@entry=0x7fffdd46f110) at kernel/qapplication.cpp:4562 #14 0x00007f6dc048830a in QApplication::notify (this=0x7fffdd46f610, receiver=0x1a0c6f0, e=0x7fffdd46f110) at kernel/qapplication.cpp:4423 #15 0x00007f6dc1b1a1d6 in KApplication::notify (this=0x7fffdd46f610, receiver=0x1a0c6f0, event=0x7fffdd46f110) at ../../kdeui/kernel/kapplication.cpp:311 #16 0x00007f6dc10dc56e in QCoreApplication::notifyInternal (this=0x7fffdd46f610, receiver=0x1a0c6f0, event=0x7fffdd46f110) at kernel/qcoreapplication.cpp:915 #17 0x00007f6dc110d462 in sendEvent (event=0x7fffdd46f110, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #18 QTimerInfoList::activateTimers (this=0x17ed690) at kernel/qeventdispatcher_unix.cpp:611 #19 0x00007f6dc110a584 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #20 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #21 0x00007f6dbb98eab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007f6dbb98ede8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007f6dbb98eea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007f6dc110abf6 in QEventDispatcherGlib::processEvents (this=0x17a34b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #25 0x00007f6dc0528c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #26 0x00007f6dc10db2bf in QEventLoop::processEvents (this=this@entry=0x7fffdd46f380, flags=...) at kernel/qeventloop.cpp:149 #27 0x00007f6dc10db548 in QEventLoop::exec (this=0x7fffdd46f380, flags=...) at kernel/qeventloop.cpp:204 #28 0x00007f6dc10e0708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #29 0x000000000041827a in main (argc=3, argv=0x7fffdd46f7c8) at ../../kpat/main.cpp:325 Reported using DrKonqi
Created attachment 79778 [details] New crash information added by DrKonqi kpat (3.6) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 Completed game of advanced spider solitaire. There was one completed suit left, which did not go down to the bottom as usual. I moved the complete suit to another column and the game crashed. This action often causes the application to recognise that the column is complete and to move it to the bottom. -- Backtrace (Reduced): #6 Spider::moveFullRunToLeg (this=0x1c52b60, pile=0x1bce2d0) at ../../kpat/spider.cpp:359 #7 0x000000000042372e in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./moc_dealer.cpp:120 #8 DealerScene::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./moc_dealer.cpp:94 [...] #12 0x00007f2757645179 in QObject::event (this=0x1c53170, e=<optimized out>) at kernel/qobject.cpp:1157 #13 0x00007f27569ae894 in notify_helper (e=0x7fff6735d520, receiver=0x1c53170, this=0x170f380) at kernel/qapplication.cpp:4559
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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 mark the bug 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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!