Too many cleanable keys that are in reality no cleanable

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start gconf-cleaner
2. the tool display 4226 total keys, and 403 cleanable keys

What is the expected output? What do you see instead?
-> the expected output for me is really only the keys that I can delete.
-> Instead I see a lot of important keys that absolutely I can't delete.
For example the connected ftp servers (Resources/Connecting server...) are
listed as cleanable keys, but if I delete these keys, I lose my ftp
connections! Other listed keys concern the Evolution resources.
If I display these keys with the GConf-Editor, the message "this key has no
schema" is diplayed, but I don't know why.
This tool, for now, can be very dangerous!

What version of the product are you using? On what operating system?
-> gconf-cleaner 0.2
-> Ubuntu Feisty 7.04

Please provide any additional information below.
- I attach the analyzing result image with the total of the keys and the
Detail with the connected server keys.

A question:
with gconf-cleaner I can save the cleanable keys before delete them in a
"reg" file. How can I import the file in gconf if I need to?
The command
gconftool-2 --install-schema-file=20070512120107.reg
don't function.

Original issue reported on code.google.com by jelmor...@gmail.com on 12 May 2007 at 12:10

Attachments:

• [Schermata-GConf Cleaner - (3 of 5).png](https://storage.googleapis.com/google-code-attachments/gconf-cleaner/issue-5/comment-0/Schermata-GConf Cleaner - %283 of 5%29.png)

[GoogleCodeExporter]

Thank you for filing an issue. appearing the connected servers issue has been
resolved in r23 though, I'm not sure if the evolution resources stuff is a bug 
in
gconf-cleaner or not, because they could have schemas for them. for example, I 
will
consider to add the name to the black list to avoid the appearance on 
gconf-cleaner
for the case like the gconf key contains the unique name e.g. the renamable 
profile
name etc, because there are no way of making schemas for such case so far. 
otherwise
it should be fixed in each applications IMHO.

If you have any other keys shouldn't be gone with gconf-cleaner, please let me 
know.

To import the saved gconf keys, see README. gconftool --load 20070512120107.reg 
would
helps for you.

Thanks,

Original comment by akira.ta...@gmail.com on 17 Jul 2007 at 4:28

• Changed state: Accepted

[GoogleCodeExporter]

Hi,

As for Evolution, at least keys regarding LDAP address books are deleted.

Cheers,
Julien

Original comment by julien.v...@gmail.com on 10 Aug 2007 at 6:50

[GoogleCodeExporter]

I suppose you are referring to /apps/evolution/addressbook/sources (and perhaps
someone may wants to say /apps/evolution/{tasks,memos,calendar}/sources too).
As other keys around it like
/apps/evolution/addressbook/completion/minimum_query_length has a schema, I 
don't see
any reasons not having a schema for /apps/evolution/addressbook/sources and the 
path
isn't even unique.
So I'd say this is a bug in evolution and I'd not have any workarounds for the
obvious bugs. please file a bug to evolution for getting fixed those keys in 
schemas.

Thanks,

Original comment by akira.ta...@gmail.com on 10 Aug 2007 at 9:40