Bug 84905 - gnect fails to load (gconf schema error)
Summary: gnect fails to load (gconf schema error)
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-games (Show other bugs)
(Show other bugs)
Version: 9
Hardware: i686 Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Jay Turner
URL:
Whiteboard:
Keywords: Triaged
: 84592 (view as bug list)
Depends On:
Blocks: 79578
TreeView+ depends on / blocked
 
Reported: 2003-02-23 16:11 UTC by Tom Vergote
Modified: 2015-01-08 00:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-07-28 21:55:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Tom Vergote 2003-02-23 16:11:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030206

Description of problem:
Trying to run the gnect game (either from menu or command prompt) produces the
following error:

The default configuration values could not be retrieved correctly. Please check
your GConf configuration, specifically that the schemas are installed correctly

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. start gnect on my box
2.
3.
    

Actual Results:  The default configuration values could not be retrieved
correctly. Please check your GConf configuration, specifically that the schemas
are installed correctly

Expected Results:  play the game

Additional info:

im running phoebe (8.0.94), upgraded from a clean 8.0.93 install

Comment 1 Jeremy Katz 2003-02-24 05:31:14 UTC
*** Bug 84592 has been marked as a duplicate of this bug. ***

Comment 2 Jeremy Katz 2003-02-24 05:46:40 UTC
Fixed in gnome-games-2.2.0-2, available at
http://people.redhat.com/~katzj/gnome-games/ for verification


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