Version: (using KDE KDE 3.1.1) Installed from: Debian testing/unstable Packages OS: Linux kpat moved the eight of clubs on to the six of clubs on the foundation, leaving the seven of clubs in the playing area. The game was still completable by moving the eight of clubs back into the playing area. I've not been able to reproduce this.
Ah-ha. This is reproducable. When kpat moves a card from the playing area to the foundation, it's possible to grab the card with the mouse and hold it inside the playing area (this may take a few tries). I suppose kpat considers the card to now be on the foundation, and proceeds to move more cards to the foundation, possibly including the next in the suit of the one you are holding. If there is still a valid place for the held card in the playing area, it can be moved there and the foundation is left corrupt. There's some more weird behaviour with this bug. E.g., if there's no valid place for the held card in the playing area, it becomes stuck and unmovable from wherever it was held when its last valid position is removed.
I think I saw the bug before. Can you please do me a favor and prepare a save game that makes it easy to reproduce this?
Created attachment 1507 [details] KPat saved game prior to foundation corruption Upon opening the saved game kpat will automatically perform several moves, undo all of them. Move the three of clubs on to the four of diamonds. KPat will automatically move the two of hearts on to the foundation, while it is in transit drag (and don't let go) the three of clubs away. KPat will move the three of clubs and the four of clubs to the foundation. If successful, you will be able to move the three of clubs from under the four of clubs to the four of diamonds, leaving the foundation corrupt. You can still continue play by moving the four of clubs back on to the five of hearts. The timing is crucial, if you try to drag the three of clubs too early then KPat will ignore the click. The best time is as the two of hearts is settling on the foundation.
*** Bug 59355 has been marked as a duplicate of this bug. ***
*** Bug 95604 has been marked as a duplicate of this bug. ***
*** Bug 97037 has been marked as a duplicate of this bug. ***
*** Bug 102954 has been marked as a duplicate of this bug. ***
Created attachment 11488 [details] bug screenshot I captured the screenshot with this. It is hard to reproduce so I don't really know how that happened. Maybe the timing is the key.
*** Bug 125337 has been marked as a duplicate of this bug. ***
BINGO! I can reproduce it :) Thanks so much Lloyd, I will only fix that for KDE4 though I guess.
SVN commit 600180 by coolo: don't allow autodrop if cards are moving BUG: 56637 M +6 -0 dealer.cpp --- trunk/KDE/kdegames/kpat/dealer.cpp #600179:600180 @@ -957,6 +957,12 @@ if (!autoDrop()) return false; + if (!movingCards.isEmpty()) { + QTimer::singleShot(qRound( TIME_BETWEEN_MOVES * m_autoDropFactor ), this, SLOT(startAutoDrop())); + return true; + } + + QList<QGraphicsItem *> list = items(); //kDebug( 11111 ) << "startAutoDrop\n";
*** Bug 81942 has been marked as a duplicate of this bug. ***
*** Bug 110621 has been marked as a duplicate of this bug. ***
*** Bug 141464 has been marked as a duplicate of this bug. ***
Something very similar happened to me today: I moved a card to the parking area and all the remaing cards begun to fly to the foundations. All but the one I parked! All the Kings on top, but an 8 remained out. I have a snapshot available, should anyone want to see it.
*** Bug 159637 has been marked as a duplicate of this bug. ***
*** Bug 158889 has been marked as a duplicate of this bug. ***