Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 97321 - gnomine high scores do not work - missing files
Summary: gnomine high scores do not work - missing files
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-games
Version: 9
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-06-12 22:39 UTC by John MacLean
Modified: 2015-01-08 00:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-09-04 11:59:42 UTC
Embargoed:


Attachments (Terms of Use)

Description John MacLean 2003-06-12 22:39:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)

Description of problem:
High scores for gnomine do not working after winning the Small and Large field 
sizes. High scores for Medium sized field does work. 
Problem appears to be incorrect filename for the gnomine.*.scores.


Version-Release number of selected component (if applicable):
gnome-games-2.2.0-3

How reproducible:
Always

Steps to Reproduce:
1.Play gnomine (preferably from a terminal)
2.Select 'Small' or 'Large' from Preferences
3.Play and win game
    

Actual Results:  1.High scores not updated and still unavailable.
2.See error message on terminal referring to missing file.


Expected Results:  Time required to win game added to high score.

Additional info:

The fix:
# mv /var/lib/games/gnomine.Tiny.score /var/lib/gnomine.Small.scores
# mv /var/lib/games/gnomine.Biiig.scores /var/lib/gnomine.Large.scores

Comment 1 Alexander Larsson 2003-09-04 11:59:42 UTC
fixed in latest rawhide.


Note You need to log in before you can comment on or make changes to this bug.