Ticket #237 (closed defect: fixed)
GConf schemas don't apply
| Reported by: | Deubeuliou | Owned by: | ppronchery |
|---|---|---|---|
| Priority: | urgent | Milestone: | rev5 |
| Component: | build | Version: | trunk |
| Severity: | major | Keywords: | |
| Cc: | prahal@… |
Description
libh1settings brings a schema file that should apply to the corresponding keys (ie, gconf should have default value for some keys)
however, using gconftool, we can see that the keys don't exist.
Change History
comment:1 Changed 2 years ago by jcassignol
- Priority changed from normal to high
- Severity changed from minor to major
comment:3 Changed 2 years ago by Deubeuliou
- Status changed from new to assigned
[1181] introduce the use of dh_gconf (sticky note: this is the recommended way to use GConf).
Now, the .schemas files end up in /usr/share/gconf/schemas
However, that doesn't close this ticket: the schemas don't apply.
On my laptop, when I ask for a value that is doesn't set (say, /desktop/h1/ui/keyboard), it returns the value that is in the schema.
On the freerunner, it raises an error stating that the key is unset.
That's why I think the problem now comes from GConf itself or it's configuration.
I'm reassigning it to Pierre.
comment:5 Changed 2 years ago by jblondon
confirmed on my freerunner, using a make install usually install gconf files but on the daily build it just does nothing. No complaints but the keys are not written.
