search

jonathasborges1 / gconf-cleaner

Automatically exported from code.google.com/p/gconf-cleaner
GNU General Public License v2.0
0 stars 0 forks source link

TREE-VIEW Request #17

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Akira, thank you for your work. 

1 - May I suggest that there should be a WARNING for the possibility of false 
candidates for removal. I hand-selected only 28 of 353 selected keys to remove. 
Most were privacy-related. The remaining were user settings that I did not want 
to lose.

2 - Rather than list every key in linear mode, if candidates for removal were 
listed in a hierarchical TREE-VIEW, users would be able to quickly recognize 
branches that should not be removed, especially user settings. This may help 
avoid problems that a growing blacklist can miss.

Original issue reported on code.google.com by roger.t.imai@gmail.com on 2 Sep 2010 at 5:06

GoogleCodeExporter commented 8 years ago 
Thank you for suggestions. that sounds nice idea to improve. unfortunately I'm 
busy and don't have certain time to work on this. that may take some time to 
get this fixed perhaps.

Original comment by ta...@gnome.gr.jp on 7 Sep 2010 at 2:30

GoogleCodeExporter commented 8 years ago 
I am a linux newbie and this program broke my system...  You really should at 
least put some kind of warning up or make it so that nothing is selected by 
default.  Now, because there is no properly functioning restore feature (even 
the command line is broken) I have to reinstall my system.  No problem, it is 
not a production system, but someone else out there might not be so lucky...

Just to make it so that this is not simply a useless rant, I will include the 
error message that is returned from the command line.

Error syncing configuration data:  Failed to contact configuration server; the 
most common cause is a missing or misconfigured D-Bus session bus daemon.  See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get 
connection to session:  Did not receive a reply.  Possible causes include:  the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the timeout expired, or the network connection was broken.)

System is Debian 6.0 Squeeze, running app as su

Cheers!

Original comment by jerald...@gmail.com on 8 Feb 2011 at 2:03

GoogleCodeExporter commented 8 years ago 
That's not a fault of this application. that error messages says it all.

Original comment by ak...@tagoh.org on 8 Feb 2011 at 2:29

GoogleCodeExporter commented 8 years ago

Original comment by ak...@tagoh.org on 8 Feb 2011 at 2:30