Bug 26872

On Sunday 14 April 2002 04:03 pm you wrote:
>                          KDE bug report logs - #26872
>                     Time isn't reset after successful game
>
>    Package: kmahjongg; Reported by: mifi at gmx de; Age: 306 days; dated
>    Thu 7 Jun 2001 12:48:01 GMT;
>    Maintainer for kmahjongg is Mathias Mueller
>    <in5y158@public.uni-hamburg.de>.
>    Send additional info to 26872 at bugs.kde.org.
>      _________________________________________________________________
>
> Message received at bugs.kde.org:
>
>    Date: 7 Jun 2001 12:36:02 -0000
>    Subject: Time isn't reset after successful game
>    From: mifi at gmx.de
>    Package: kmahjongg
>    Version: KDE 2.1.1
>    Severity: normal
>    Installed from: SuSE RPMs
>    Compiler: Not Specified
>    OS: Linux
>    OS/Compiler notes: Not Specified
>    If a game ends successfully a new board is displayed and a new game
>    starts therewith. But the clock isn't reset to 0 so it's not possible
>    to compete again with this following game.
>    (Submitted via bugs.kde.org)
>      _________________________________________________________________
>
>    Acknowledgement sent to mifi at gmx.de:
>    New bug report received and forwarded. Copy sent to Mathias Mueller
>    <in5y158 at public.uni-hamburg.de>. Full text available.
>      _________________________________________________________________
>
>    Report forwarded to kde-bugs-dist at master.kde.org Mathias Mueller
>    <in5y158@public.uni-hamburg.de>:
>    Bug#26872; Package kmahjongg. Full text available.
>      _________________________________________________________________
>
>
>     Stephan Kulow / owner@bugs.kde.org through the KDE bug database
>
>    Last modified: 05:39:02 GMT Wed 10 Apr (timestamp page available).

Patch supplied by Peter Nimmervol (vanHell@gmx.at).  Change commited to CVS 
on 4/13/02.

Thank you for your bug report.
The bug that you reported has been identified and has been fixed in the
latest development (CVS) version of KDE. The bug report will be closed.

*** Bug 46096 has been marked as a duplicate of this bug. ***