On Mon, Feb 19, 2018 at 10:29 AM, Stan Brown
wrote:
> On 2018-02-10 10:37, Stan Brown wrote:
>
> I can't see any reason why uninstalling and reinstalling the program
> would have fixed the problem with crashing on report production (or very
> slow performance). And it
On 2018-02-10 10:37, Stan Brown wrote:
> I installed Gnucash 2.6.19 (from link at Gnucash.org) on my 64-bit
> Windows 7 laptop and 64-bit Windows 8 laptop and started working my way
> through the tutorial. ... I attempted to display the report of scheduled
> transactions. Got only a blank window,
id Carlson<david.carlson@gmail.com>
To: Ken Pyzik<py...@cox.net>
Cc: Stan Brown<the_stan_br...@fastmail.fm>, Gnucash Users
<gnucash-user@gnucash.org>
Subject: Re: Reports crash Gnucash
Message-ID:
<cadygsbncotumupeap8rkhovtcdkz8mxxhrvoupb-kb0-oh_...@mai
So, I went back to bug 645273, and I'd have to say that it describes a
different problem altogether. That problem dealt with reports not rendering in
Windows. The implication in all of the comments there is that program was
functioning but not producing data. That's different from the program
I forgot to mention that progress bar at the bottom of the main window.
That also shows the progress of the file save activity.
David C
On Sat, Feb 10, 2018 at 8:04 PM, John Ralls wrote:
> The progress bar for reports started with the main window displayed is at
> the
The progress bar for reports started with the main window displayed is at the
bottom right of that window.
Regards,
John Ralls
> On Feb 10, 2018, at 5:51 PM, David Carlson
> wrote:
>
> doncram,
>
> Actually, if you look carefully at the bottom of the splash
doncram,
Actually, if you look carefully at the bottom of the splash screen (if you
have not disabled it) when the program is loading, there is a message
there. That will show when processing reports that were left open when the
file was last closed.
As for opening new reports, I cannot comment
If there's no functional bug, then there's a different bug: what is
displayed should be changed to show "report processing...please allow a few
minutes" or something like that. Surely it should not take seven years to
change what a message states. --doncram
On Sat, Feb 10, 2018 at 5:32 PM, Ken
Stan,
I am sorry that your experience with GnuCash has not been favorable.
I suspect that you may not have gotten the correct release of 2.6.19 for
windows as I think there was a glitch early on that caused the crashing
when opening reports that you mention. I believe the bug that you were
Stan -- I am using 2.6.19 on 64-bit Windows 10. While the reporting module
is indeed very slow (bug report already out there was this) and while it
does say "Not Responding", eventually the report does come up (after about
60-90 seconds).
I agree that it may be way too long -- but it does
10 matches
Mail list logo