[GNC] GNU crashes when any Report is selected

[David Carlson]

The 'not responding' message is from Windows and it has no clue why GnuCash
is not responding.  It would be nice if Windows signed the message so we
know where it is from.  Unfortunately, many programs behave like they are
the only ones on the planet and users should 'just know'

David C

On Mon, Dec 10, 2018 at 12:12 PM Arnie Reeves via gnucash-user <
gnucash-user at gnucash.org> wrote:

> Tend to agree Stephen regarding the possible effects of MS updates. My
> reports have always opened within a couple of seconds, that's why I thought
> 1 to 2 minutes was a crash. It would be nice for beginners to see a small
> text next to the "GNUCash not responding" message to advise them to wait
> longer. The gut feeling of "external influences" was immediate which is why
> I thought that reinstalling would perhaps fix a contaminated file. John's
> experience was of course correct in identifying a hang rather than a crash,
> and I'm grateful for his sound advice, but it's strange that this long
> delay was so suddenly  imposed. I could understand a gradual progressive
> delay as files got bigger.
> Arnie
>
> -----Original Message-----
> From: gnucash-user <gnucash-user-bounces+karndale=
> blueyonder.co.uk at gnucash.org> On Behalf Of Stephen M. Butler
> Sent: 10 December 2018 17:47
> To: gnucash-user at gnucash.org
> Subject: Re: [GNC] GNU crashes when any Report is selected
>
> On 12/10/18 4:46 AM, Stan Brown wrote:
> > Hi, Arnie.
> >
> >> Date: Sun, 9 Dec 2018 16:27:01 -0000
> >> From: "Arnie Reeves" <karndale at blueyonder.co.uk>
> >> To: "'David Carlson'" <david.carlson.417 at gmail.com>
> >>
> >> Thank you for your response David, suggesting ?other? program updates on
> >> my Windows 10 set up, including a recent upgrade to MS Office 2019 which
> >> includes Access, may be responsible for causing my GNUCash 2.6.19 to
> >> crash every time I select a report. That being the only suggestion (so
> >> far), I believe my only option is to reinstall the GNUCash program, and
> >> keep fingers crossed.
> > You sound perhaps a bit skeptical of David's blaming your troubles on
> Windows 10 updates, so I thought I'd offer my perspective. Based on my
> experience at work (I do customer support for a company that sells
> application software to run in Windows), I have no trouble at all believing
> that David has put his finger on it.
> >
> > We are seeing a LOT of cases where our software is working on Windows 10
> computers, Windows or Office or both do an automatic update, and our
> software stops working. We spend weeks trying to troubleshoot some of
> these, and often we're unable to fix them because the cause is that
> Microsoft's own updates have broken a piece of its Windows or Office
> software.  GnuCash is fortunate in not being directly dependent on Excel,
> but Office updates update Windows code and vice versa, so either type of
> update can cause a problem in Windows or Office or both.
> >
> > The pace of these "updatogenic" problems is accelerating in a
> frightening way. A time may come when it's simply impossible to keep
> application programs working in Windows 10, or at least where you can
> expect to spend more time finding help with problems caused by Microsoft
> updates than you do actually using your software.
> >
> > One thing you can do to reduce your exposure is to make sure you're not
> in "Windows Insider", "Office Insider" or any other "Insider". Those update
> schedules get you updates that Microsoft doesn't even pretend to have
> tested adequately. Some problems are caught at that stage, so that the
> monthly updates are less buggy than they would be otherwise. Not that the
> monthly updates are bug free by any means, but they're usually not as bad
> as the Insider builds.
> >
> This morning my wife received an email with a couple of attached jpeg
> images.  She tried to print from Windows 10.  I saw them go through the
> print queue but nothing ever printed from the printer.
>
> Finally, she forwarded the email to me (on a Ubuntu box) and I was able
> to print them without problems.  Same printer.  Same network.  Same
> images.  Windows 10 just "lost" the file on the way to the printer.
> Ubuntu got them all the way to the printer.
>
> Neither system involved GnuCash.  So, my take is that it is a Windows 10
> problem that I'm sure Microsoft will put the blame on the printer!
>
>
>
> --
> Stephen M Butler, PMP, PSM
> Stephen.M.Butler51 at gmail.com
> kg7je at arrl.net
> 253-350-0166
> -------------------------------------------
> GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>