Thanks for the report!
- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdegames-dbg" package and post a complete backtrace here? (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) Thanks

Created attachment 39541 [details]
Traceback of crash.

It took a while but here is a traceback (this was an initial selection of Grandfather after starting Kpat).

Pasting backtrace inline:
---

Application: KPatience (kpat), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  GrandfSolver::get_possible_moves (this=0xdb11a0, a=0x7fff39f5927c, numout=0x7fff39f59278) at /build/buildd/kdegames-4.3.2/kpat/patsolve/grandf.cpp:257
#6  0x000000000043e5fe in Solver::get_moves (this=0xdb11a0, nmoves=0x7fff39f592bc) at /build/buildd/kdegames-4.3.2/kpat/patsolve/patsolve.cpp:211
#7  0x000000000043e9cd in Solver::solve (this=0xdb11a0, parent=0xdec0a8) at /build/buildd/kdegames-4.3.2/kpat/patsolve/patsolve.cpp:682
#8  0x000000000043f44b in Solver::doit (this=0xdb11a0) at /build/buildd/kdegames-4.3.2/kpat/patsolve/patsolve.cpp:639
#9  0x000000000043f4a7 in Solver::patsolve (this=0xdb11a0, _max_positions=<value optimized out>) at /build/buildd/kdegames-4.3.2/kpat/patsolve/patsolve.cpp:929
#10 0x0000000000421350 in DealerScene::getSolverHints (this=0xccf450) at /build/buildd/kdegames-4.3.2/kpat/dealer.cpp:663
#11 0x0000000000421541 in DealerScene::getHints (this=0xdb11a0) at /build/buildd/kdegames-4.3.2/kpat/dealer.cpp:693
#12 0x000000000042468f in DealerScene::startAutoDrop (this=0xccf450) at /build/buildd/kdegames-4.3.2/kpat/dealer.cpp:1348
#13 0x000000000042b9fb in DealerScene::qt_metacall (this=0xccf450, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff39f596d0)
    at /build/buildd/kdegames-4.3.2/obj-x86_64-linux-gnu/kpat/dealer.moc:135
#14 0x0000000000457d85 in Grandf::qt_metacall (this=0xdb11a0, _c=972395132, _id=972395128, _a=0xf72434) at /build/buildd/kdegames-4.3.2/obj-x86_64-linux-gnu/kpat/grandf.moc:64
#15 0x00007f75c88cbddc in QMetaObject::activate (sender=0xcd8410, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xf72434) at kernel/qobject.cpp:3113
#16 0x00007f75c88c5d83 in QObject::event (this=0xcd8410, e=0x7fff39f5927c) at kernel/qobject.cpp:1075
#17 0x00007f75c9447efc in QApplicationPrivate::notify_helper (this=0xb29a70, receiver=0xcd8410, e=0x7fff39f59cd0) at kernel/qapplication.cpp:4056
#18 0x00007f75c944f1ce in QApplication::notify (this=0x7fff39f5a130, receiver=0xcd8410, e=0x7fff39f59cd0) at kernel/qapplication.cpp:4021
#19 0x00007f75ca838ab6 in KApplication::notify (this=0x7fff39f5a130, receiver=0xcd8410, event=0x7fff39f59cd0) at ../../kdeui/kernel/kapplication.cpp:302
#20 0x00007f75c88b6c2c in QCoreApplication::notifyInternal (this=0x7fff39f5a130, receiver=0xcd8410, event=0x7fff39f59cd0) at kernel/qcoreapplication.cpp:610
#21 0x00007f75c88e1862 in QCoreApplication::sendEvent (this=0xb4b600) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#22 QTimerInfoList::activateTimers (this=0xb4b600) at kernel/qeventdispatcher_unix.cpp:572
#23 0x00007f75c88df25d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#24 0x00007f75c4b97bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007f75c4b9b598 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007f75c4b9b6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007f75c88df1a6 in QEventDispatcherGlib::processEvents (this=0xaec5f0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#28 0x00007f75c94dc4be in QGuiEventDispatcherGlib::processEvents (this=0xdb11a0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#29 0x00007f75c88b5532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007f75c88b5904 in QEventLoop::exec (this=0x7fff39f59f70, flags=) at kernel/qeventloop.cpp:201
#31 0x00007f75c88b7ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0x000000000041657c in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdegames-4.3.2/kpat/main.cpp:267

This could be related to bug 214479, which was fixed recently...
@Parker: what do you think ?
Thanks

@Dario: This indeed looks similar to bug 214479, but that bug was introduced  *after* KDE4.3. I'm going to leave the bug open, but unconfirmed for the time being.

@James: When you get a chance to upgrade to KPat 3.3 (in KDE SC 4.4), could you try to reproduce?

Are you still able to reproduce this bug? If not, I would say it can be safely closed.

(In reply to comment #6)
> Are you still able to reproduce this bug? If not, I would say it can be safely
> closed.

It looks to be fixed in V4.4.x

Thanks.