After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 57946 - Gnome Tali multiple additions to high score list
Gnome Tali multiple additions to high score list
Status: RESOLVED DUPLICATE of bug 3946
Product: gnome-games-superseded
Classification: Deprecated
Component: gtali
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Games maintainers
Gregory Leblanc
: 57947 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-07-23 20:14 UTC by Jonathan Blandford
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonathan Blandford 2001-07-23 20:14:30 UTC
[ Forwarded from RH bug tracker ]

Description of Problem:

Often when I get a new top-ten score in Gnome Tali (/usr/bin/gtali), the
score is added to the high score list several times.  A top ten score list
window pops up for each addition. For example, I just got a new top-ten
score (tying the previous highest score), and six Top Ten windows popped
up.  One shows the new score added to the list once, one twice, one three
times,... the last six times.

How Reproducible:

Get a new top-ten score in Gnome Tali. Does not always happen.

Steps to Reproduce:
1. Win the game with a new top-ten score.
2. 
3. 

Actual Results:

One new entry in the top ten, and one Top Ten window.

Expected Results:

Several, as describe above.

Additional Information:

This bug has been around through many Red Hat versions -- possibly since
the first GNOME release; I'm not sure.
Comment 1 Gregory Leblanc 2001-11-16 06:35:14 UTC
*** Bug 57947 has been marked as a duplicate of this bug. ***
Comment 2 Gregory Leblanc 2001-11-16 06:36:27 UTC
Isn't some of this code shared between games?  Oh, maybe the scores
thing was in gnome-libs...  
Comment 3 Luis Villa 2002-02-14 01:51:48 UTC

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