MacOS cannot save settings

[David T.]

John--

I confirm that the file you reference below has numerous references to /opt/gnucash-2.3.x/etc/gconf/2/ on my 2.4.0 installation. There's nothing about Users/John. 

I haven't yet loaded 2.4.3, but I imagine that's still there.

David

--- On Wed, 3/9/11, John Ralls <jralls at ceridwen.us> wrote:

> From: John Ralls <jralls at ceridwen.us>
> Subject: Re: MacOS cannot save settings
> To: "John Ralls" <jralls at ceridwen.us>
> Cc: gnucash-user at gnucash.org
> Date: Wednesday, March 9, 2011, 8:30 PM
> 
> On Mar 9, 2011, at 8:11 PM, John Ralls wrote:
> 
> > 
> > On Mar 9, 2011, at 12:22 PM, Michael wrote:
> > 
> >> Hi,
> >> As I read the contents of the "path"-file, it
> searches for a default file, if it cant find the user's
> settings file. 
> >> But as i can see, there is no /opt/gnucash-2.3.x
> directory. 
> >> 
> >> What can I do?
> >> 
> > 
> > That's really bizarre. Gnucash hasn't used
> /opt/gnucash-2.3.x since 2.3.8, over a year ago, and I don't
> think that GConf has used .gconf.path in quite a while,
> either.  The 2.4.3 I just launched didn't seem to need
> either (meaning that I deleted the ancient remnants of both
> and launched Gnucash-2.4.3 and it started up with the last
> accounts file I had had open and appeared to have my
> preferences set correctly. When I quit Gnucash, neither
> ~/.gconf.path and /opt existed. 
> > 
> > Try deleting .gconf.path 
> 
> Hmm, digging a bit deeper, I see that the path file is now
> in the bundle, at
> Gnucash.app/Contents/Resources/etc/gconf/2/path, and that it
> might very well be hard-coded to
> /Users/john/Library/Gnucash-2.4/etc/gconf.
> 
> See it that's the case on  yours, and if it is, try
> editing that file to point to your Library instead.
> 
> Regards,
> John Ralls
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>