Date: Thu, 24 Jun 2010 16:30:57 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Kevin Oberman" <oberman@es.net> Cc: gnome@freebsd.org Subject: Re: Problems with configuration files after multiple Gnome upgrades Message-ID: <op.vetp2jnl9aq2h7@localhost> In-Reply-To: <20100623192906.406641CC0D@ptavv.es.net> References: <20100623192906.406641CC0D@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Jun 2010 14:29:06 -0500, Kevin Oberman <oberman@es.net> wrote: > After the upgrade to Gnome 2.30, various of my systems had a variety of > "odd" issues. The most serious was the inability of gnome-screensaver to > get a password and unlock. Two of my systems had this problem. > > Other issues included gnome-power-manager failing to exit on logout, the > menu editor (alacarte) changes taking not instantiating until the panel > is restarted and several other slightly misbehaving things. > > I removed .gnome2, .local, and .config. This fixed many problems, but > not all. To fix the screensaver issue, I had to delete an old .xmodmap, > of all things. I just stumbled across this. > > Is there anyplace to look for a list of files that save Gnome > configuration? At least those used by standard apps? I hate to have to > configure from scratch, but I'm much happier now that I have done so, at > least for the stuff I could find. At the every release of GNOME, I always clear out all of .* configuration files/folders to get my GNOME desktop runs reliable while others don't have to. Why? What's wrong w/ it? I dunno. Sorry, it's not exactly useful reply but it's all I can say. Cheers, Mezz > (I'd just love to know how .xmodmap broke the screensaver.) -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.vetp2jnl9aq2h7>