gconf-schemas --unregister not removing empty /apps/appname

[Francesco Fumanti]

Hello,

Suppose that we have a file called mytesting.schemas with the following content:

<gconfschemafile>
  <schemalist>
    <schema>
      <key>/schemas/apps/my_app/my_key</key>
      <applyto>/apps/my_app/my_key</applyto>
      <owner>my_app</owner>
      <type>int</type>
      <default>42</default>
      <locale name="C">
        <short>A short description of this key</short>
        <long>A longer description here. We can have lots of text
           here, describing what the possible values are, and what
            they mean.
        </long>
      </locale>
    </schema>
    <schema>
      <key>/schemas/apps/my_app/my_other_key</key>
      <applyto>/apps/my_app/my_other_key</applyto>
      <owner>my_app</owner>
      <type>bool</type>
      <default>1</default>
      <locale name="C">
        <short>A short description of this key</short>
        <long>A longer description here. We can have lots of text
      here, describing what the possible values are, and what
          they mean.
        </long>
      </locale>
    </schema>
  </schemalist>
</gconfschemafile>

The following command in the terminal registers the schemas in the gconf database:
sudo gconf-schemas --register /path/to/mytesting.schemas

The following command in the terminal only partially removes the keys from the gconf database:
sudo gconf-schemas --unregister /path/to/mytesting.schemas

In fact, /schemas/apps/my_app and /apps/my_app remain listed in the gconf database.

However, the command "sudo gconf-schemas --register-all" called after the unregister command, makes /schemas/apps/my_app and /apps/my_app disappear from the gconf database.

Should /schemas/apps/my_app and /apps/my_app not already disappear with the gconf-schemas --unregister command?

Cheers

[Sebastien Bacher (seb128)]

thank you for your bug report, did you restart your session or gconf after the unregister? does using gconftool directly work correctly?

[Francesco Fumanti (frafu)]

/schemas/apps/my_app and /apps/my_app remain listed in the gconf-editor even after restarting the session.

Could you please give me the exact gconftool command to use?

I tried for example
sudo gconftool-2 --recursive-unset /apps/my_app
but it did not remove anything.

[Sebastien Bacher (seb128)]

you can look to gconf-schemas to see the command it's called, it seems to be using --makefile-uninstall-rule on the schemas and specify the GCONF_CONFIG_SOURCE directory to use too

[Pedro Villavicencio (pedro)]

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.