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 137044 - GConf schemas unreadable
GConf schemas unreadable
Status: RESOLVED DUPLICATE of bug 136400
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: High blocker
: 0.8.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-13 08:43 UTC by Matthew Schick
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Matthew Schick 2004-03-13 08:43:41 UTC 
Gconf settings are installed under '/schemas/system/gstreamer/0.8/' which
seems to be unreadable by GConf-2.5.90 due to the decimal point.  Moving
those settings to '/schemas/system/gstreamer/0_8/' and gconf becomes happy...
Comment 1 Thomas Vander Stichele 2004-03-13 14:14:54 UTC 
That's weird.  Here it shows up fine.  How certain are you that this
is really the problem ? any piece of code I can look at ?
Comment 2 Matthew Schick 2004-03-13 17:17:41 UTC 
I don't have any code to show, but I have a screenshot of the behavior
here: http://breakmygentoo.net/gstreamer-gconf.png

As you can see, the default 0.8 is empty while the 0_8 has the
expected structure.  I tried recompiling with DIR_CFLAGS =
-DGST_GCONF_DIR=\"/system/gstreamer/0_8\" in the Makefile, and
gstreamer-properties actually found and set my sinks as it should have.
Comment 3 Max Nickel 2004-03-13 17:30:04 UTC 
same problem here, /schemas/system/gstreamer/0.8/ shows up but is empty,
didn't test Matt's solution though
Comment 4 Christian Fredrik Kalager Schaller 2004-03-15 09:16:58 UTC 
*** Bug 136400 has been marked as a duplicate of this bug. ***
Comment 5 Christian Fredrik Kalager Schaller 2004-03-15 09:18:15 UTC 
Marking my bug of as a duplicate of this bug as the screenshot shows 
it is the exact same issue I reported. Marking this as a 0.8.0 
blocker.
Comment 6 Thomas Vander Stichele 2004-03-15 22:57:54 UTC 

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