kpatience gypsy closes randomly and unexpectedly

[Dale Trombley]

running kpat from terminal, returns the following:

lorraine@lorraine-Aspire-5733Z:~$ kpat
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/lorraine/.config/ibus/bus
KCrash: Application 'kpat' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/lorraine/.kde/socket-lorraine-Aspire-5733Z/kdeinit4__0
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
kpat: Fatal IO error: client killed
Unable to start Dr. Konqi

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: kpat 4:4.7.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Fri Aug 26 17:06:15 2011
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kdegames
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dale Trombley (buzzmandt)]

Also affects Kubuntu oneiric 11.11 with kde 4.7.2

[Stuart Kirby (stuart-kirby20)]

I have experienced this problem many times since downloading UBUNTU 11.10.

It seems to be associated with the "solver" in that I am taking no actions and suddenly it crashes. I would say that it only crashes when the game looks easy to solve! One repeatable example is as follows:

Choose "new numbered deal", Gypsy, number: 102194206
Move 7 of spades to 8 of hearts, 8 of hearts to 9 of clubs, 5C to 6D, 6D to 7C - boom!
Also: 7S to 8H, 8H to 9C, 5C to 6D, 6D to 7S, 2S to space, 6Hh to 7C .......boom!

I have notice different Gypsy games where it fails shortly after the deal before any card has been moved.

[Dale Trombley (buzzmandt)]

Been testing with and without 'enable solver' enabled. if enabled seems to crash most of the time you can win this hand. If not enabled, so far hasn't crashed for a week solid. I'd have to say definitely in the enable solver code.

[Stuart Kirby (stuart-kirby20)]

I agree. It always seems to fail when the hand looks promising. Also,
I have been playing without "enable solver" and it has not failed.

On 12/11/11 23:39, buzzmandt wrote:
> Been testing with and without 'enable solver' enabled. if enabled seems
> to crash most of the time you can win this hand. If not enabled, so far
> hasn't crashed for a week solid. I'd have to say definitely in the
> enable solver code.
>