GnuCash 2.4.0 in Intel MacBook Pro hangs

[David T.]

If this is truly what caused your upgrade problem, then I think this should be entered as a bug (if it isn't already), not as documentation. Gnucash really shouldn't hang if it can't open a report for ANY reason; it should skip opening it and keep loading.

David

--- On Mon, 12/27/10, Peter Boosten <peter at boosten.org> wrote:

> From: Peter Boosten <peter at boosten.org>
> Subject: Re: GnuCash 2.4.0 in Intel MacBook Pro hangs
> To: "Peter Boosten" <peter at boosten.org>
> Cc: gnucash-user at gnucash.org
> Date: Monday, December 27, 2010, 7:00 AM
> 
> On 23 dec 2010, at 07:20, Peter Boosten wrote:
> 
> > Hi all,
> > 
> > I've installed (or upgraded to) 2.4.0, accroding the
> readme in the dmg file.
> > 
> > First removed the 2.2.9 version, then ran the Update
> Dirs tool, which gave me some error messages about things I
> didn't have installed (like online banking). I assumed these
> were oke.
> > 
> > Then copied Gnucash to applications, and started it.
> > 
> > Gnucash wasn't happy with the changes made by Update
> Dirs apparently, since it stated that it had to change
> configuration as well, so I let it.
> > 
> > After that, gnucash showed my default opened accounts
> and reports, however hangs immediately after that, and I'm
> only able to force quit the app.
> > 
> > Anyone know how to circumvent/solve this issue?
> 
> Oke, it turned out to be the opened reports: I quit 2.2.9
> with some reports opened, and installed 2.4.0 afterwards
> (after converting the config information). I started anew,
> with 2.2.9 not showing the reports, then did the whole
> installation procedure again, and everything worked.
> 
> Maybe something to mention in the upgrade document?
> 
> -- 
> Peter Boosten
> http://www.boosten.org
> 
> 
> 
> _______________________________________________
> 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.
>