Bug 169337 - klondike demo places cards wrong
Summary: klondike demo places cards wrong
Status: RESOLVED DUPLICATE of bug 165916
Alias: None
Product: kpat
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-18 07:57 UTC by Michael Burger
Modified: 2008-09-10 11:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
screenshot (81.17 KB, image/png)
2008-08-18 08:04 UTC, Michael Burger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Burger 2008-08-18 07:57:46 UTC
Version:            (using KDE 4.1.0)
Compiler:          gcc 4.2.1 
OS:                Linux
Installed from:    Compiled From Sources

Steps to reproduce:
1, Change the game type to klondike.
2. Find a game where there is an Ace to be put up time
3. Restart the game and while it's being delt press demo.

I have been able to reproduce this many times.
I will attach a screenshot of what happens.
Comment 1 Michael Burger 2008-08-18 08:04:52 UTC
Created attachment 26903 [details]
screenshot
Comment 2 Michael Burger 2008-08-18 08:41:25 UTC
For testing I'm using game number 650803733. Sometimes it happens and sometimes it doesn't. When trying with a debug build I get a crash with the backtrace:
Application: KPatience (kpat), signal SIGABRT

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb54e86f0 (LWP 20733)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (process 20733)]

Thread 1 (Thread 0xb54e86f0 (LWP 20733)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb66d16f6 in nanosleep () from /lib/libc.so.6
#2  0xb66d150b in sleep () from /lib/libc.so.6
#3  0xb7b1623a in ?? () from /opt/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 3 Stephan Kulow 2008-09-10 11:49:27 UTC

*** This bug has been marked as a duplicate of bug 165916 ***