Brian Cameron writes: > If running gnome-cleanup fixes a problem, this means that you have > found a problem with how GNOME's configuration management isn't > supporting backwards compatibility as well as it should.
OK. > If you > are using the vermillion-devel builds, this may or may not be a > real problem. I am not. I am using the gnome bundled with SXCE. > If you were able to identify specifically which configuration option > is causing the problem, then we can work the external GNOME/FreeDesktop > community to better support backwards compatibility. The problem with > figuring out more specifically what the problem might be is that it can > be labor intensive. Let me explain. [ ... procedure snipped ] I'll attempt the procedure you suggested (though avoiding the fork-in-my-eye bit), and see if I can't get a helpful bug filed. > If this process makes you want to stick a fork in your eye, then > perhaps you understand why many people run gnome-cleanup and > forget about it. Though perhaps other people might have better > approaches or suggestions about how to debug such problems? Being able to understand what gconf keys are looked up when an application is launched might help. (I suspect that with a little effort, DTrace would help.) However, I'm not exactly sure whether that'd help when the problems are fairly global (e.g. *all* window title bars are effected), like mine usually are. Being able to get a list of where the user/app-specified changes vary from the system defaults would also help. Do you have a directory of gconf defaults I can just diff things against as a start? (Not that this doesn't have parallels in other parts of the system. ;) ) Combining the two in a single command would be powerful. liane
