gnucash-user Digest, Vol 176, Issue 58

Ian McAllister purchase at smarthomebiz.com
Wed Nov 29 08:21:24 EST 2017


Thanks Colin,

The irony of it is that it was the backup that caused the trouble!

I think I cloned a blank file onto my hard drive instead of the other 
way around, which meant replacing Windows 10. Fortunately I had a clone 
in the Garage taken a week earlier - I clone the drive nightly, and once 
a week I clone it on a different drive to go out in the garage.

The technician had to try three times to re-install windows before he 
succeeded. It takes me about two weeks to re-install all my programs 
with the serial numbers and identity keys, and at the end of the second 
week my computer crashed again, and this time it wasn't an intermittent 
problem - the motherboard and two other bits of hardware had to be 
replaced. So I asked the technician to partition the drive into four. 
Then if Windows crashed again it would only affect the home partition.

When I had the basic programs installed, I tried to clone the hard 
drive, and was told that it can only clone up to three partitions. I use 
the AOMEI backerupper which has a free version that does what you need. 
So I looked for an open-source program to clone my drives. It seemed 
that Clonezilla and Yumi would be the ideal combination, so I got them 
and cloned my drive.

Was I in trouble?! Apparently that arrangement changes the format of the 
home hard drive as well as the clone, so that it can only be run through 
YUMI - if Yumi is working - which it wasn't.

So there I was with in inoperable hard drive and a clone that wasn't 
formatted for NTFS so Windows couldn't use it.

Then I remembered my cheap and nasty laptop computer. I discovered how 
to use DiskPart to recover USB sticks or hard drives and had several USB 
sticks that didn't work. So I selected each memory stick in turn, 
cleaned it, selected the volume and reformatted as one partition only.

It worked over and over again, so I decided to try it on my cloned 
drive. It worked, once I had learned to include QUICK in the command 
format quick fs=ntfs to avoid waiting several days to complete the format.

At that stage I had a computer hard drive that was incorrectly 
formatted, a blank hard drive in an USB docking station, and a lap-top. 
So I formatted a 1TB memory stick as NTSF, transferred the computer hard 
drive to the docking station, copied each of the last three partitions 
onto a folder in the memory stick, so that the data would be in a root 
folder which contained three data folders instead of four partitions. 
For the root folder, I only copied the non-windows folders to avoid 
conflict with Windows. Then I duplicated the USB memory stick onto the 
blank hard drive.

Now I had two backups, so I re-installed Windows, made sure that it was 
running correctly and formatted as NTFS, then copied my backup hard 
drive information back to the computer hard drive.

I bought another hard drive for the USB docking station, and cloned the 
computer drive in 32minutes 38 seconds.  I removed the computer hard 
drive, and plugged in the cloned hard drive in its place, and everything 
booted up nicely.

So, now I have one computer hard drive updated, one cloned updated hard 
drive, and one hard drive with all the old partitions. I'll keep that 
until I'm convinced that I won't need to find important data on it - 
such as gnucash. Once I feel safe again, I'll keep a daily clone on the 
computer, and a weekly clone out in the garage. The advantage of having 
clones (if they work) is that I'll never again have to remember where I 
put the gnucash data files. If one hard drive becomes faulty, I'll just 
boot up from another clone.

Now, I only have to re-install a heap of other programs. I've already 
installed MS Office, Open Office, Photoshop, Lightroom, Adobe Premiere 
Elements, GnuCash, color picker, and icons in the task bar for 
restarting the computer and for stopping it. I've installed Thunderbird, 
Firefox, Chrome, Opera, and Roboform, and tracked down the bookmarks and 
data where needed.

I know the value of backups - I just lost several thousand photos for 
Stock Photos when the clone software cloned over the top of a memory 
stick. I don't know how that happened, but it means that I'll have to 
start again from scratch, taking photos. And backing up the memory stick 
is painful - it starts off saying that it can copy everything in five 
hours, then three hours, then a day, then two days, then indefinitely, 
as the transfer keeps slowing down. There must be a faster way, but I 
haven't found it yet.

Ian McAllister


On 29/11/2017 05:05 PM, Colin Law wrote:
> Now that you have found them do remember to make regular backups to a
> removable usb drive or something, that is not permanently plugged into
> your computer, and also backup any other important files/documents you
> have. Remember that a PC or drive can go up in smoke (literally or
> metaphorically) at any time, taking your data with it. You should also
> have an occasional offsite backup in case of fire/theft or similar
> catastrophe.
>
> Colin
>
> On 29 November 2017 at 07:36, Ian McAllister <purchase at smarthomebiz.com> wrote:
>> A big thanks to everybody who tried to help me to recover from the crash.
>> It's fixed!
>>
>> The trouble is that I don't have a good enough memory for the half-million
>> files on my hard drive.
>>
>> I just spotted that I had two folders in my data folder (which doesn't get
>> wiped each time that Windows crashes) for personal accounts and business
>> accounts. All that I needed to do was to reinstall GnuCash then tell it to
>> open file. Then I had to navigate to one of the two discovered folders and
>> open the folder - not one of the files. Then I did the same with the other,
>> and everything is set up again.
>>
>> Now I've re-named the files with gnucash in the name which might help my
>> memory - e.g. AccountsBusinessGnucash2017
>>
>> Thanks for your help - I hated the idea of re-entering half a year of
>> bookkeeping.
>>
>> Ian McAllister
>>
>>
>> On 29/11/2017 01:00 AM, gnucash-user-request at gnucash.org wrote:
>>> Send gnucash-user mailing list submissions to
>>>          gnucash-user at gnucash.org
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>          https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> or, via email, send a message with subject or body 'help' to
>>>          gnucash-user-request at gnucash.org
>>>
>>> You can reach the person managing the list at
>>>          gnucash-user-owner at gnucash.org
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of gnucash-user digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>      1. Re: Gncash 2.6.17 crash on Mac Os High Sierra 10.13.Beta
>>>         (Alexis Lucena Torrellas)
>>>      2. Re: gnucash-user Digest, Vol 176, Issue 55 (Frank H. Ellenberger)
>>>      3. Feedback for 2.7.2 on Windows (Alen Siljak)
>>>      4. Re: Alphavantage not working in gnucash 2.6.17 (John Ralls)
>>>      5. MacOS Sierra - Upgrade Problems (Fiona Vella)
>>>      6. Re: GnuCash release numbering (Alan Whiteman)
>>>      7. Re: MacOS Sierra - Upgrade Problems (Gerry Starnes)
>>>      8. Re: MacOS Sierra - Upgrade Problems (Christoph R)
>>>      9. Re: MacOS Sierra - Upgrade Problems (Fiona Vella)
>>>     10. Re: Alphavantage not working in gnucash 2.6.17 (Patrick Alken)
>>>     11. Slow startup on Windows 10, v2.6.18 (Steve Goings)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Tue, 28 Nov 2017 07:01:13 -0400
>>> From: Alexis Lucena Torrellas <alexislucena65 at gmail.com>
>>> To: Christoph R <subscriptions+listen at rohland.net>
>>> Cc: gnucash-user at gnucash.org
>>> Subject: Re: Gncash 2.6.17 crash on Mac Os High Sierra 10.13.Beta
>>> Message-ID: <69CA103B-6188-4797-A488-B80DB894695A at gmail.com>
>>> Content-Type: text/plain;       charset=utf-8
>>>
>>> Thank you very much, I did it and I can use the program again ... I do not
>>> know how much I appreciate it, I thank you very much ...
>>>
>>> Blessings!
>>>
>>>> El 28 nov. 2017, a las 6:32 a. m., Christoph R
>>>> <subscriptions+listen at rohland.net> escribi?:
>>>>
>>>> Use the current release (2.6.18). It is out there
>>>>
>>>> Cheers,
>>>> Christoph
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Tue, 28 Nov 2017 14:51:13 +0100
>>> From: "Frank H. Ellenberger" <frank.h.ellenberger at gmail.com>
>>> To: helpian at smarthomebiz.com, gnucash-user at gnucash.org
>>> Subject: Re: gnucash-user Digest, Vol 176, Issue 55
>>> Message-ID: <35437b2a-d92f-0b07-dd39-b8e3fa8caf9e at gmail.com>
>>> Content-Type: text/plain; charset=utf-8
>>>
>>> Am 28.11.2017 um 04:44 schrieb Ian McAllister:
>>>> Thanks David,
>>>>
>>>> I searched my backup disk, and found 473 instances of .gnucash but no
>>>> files with the right name, but without the .gcm at the end.
>>>>
>>>> I suppose I'll just have to start with a new installation, and put in
>>>> data from my bank for five months.
>>>>
>>>> Ian McAllister
>>> If you have a copy of the windows registry in your backup, search it for
>>> keys similar to "org.gnucash.history" file0 ... should contain the path
>>> of your recent used data files.
>>>
>>> Usually they should be in your home directory, but not in its .gnucash
>>> directory.
>>>
>>> HTH
>>> Frank
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 3
>>> Date: Tue, 28 Nov 2017 14:53:16 +0100
>>> From: "Alen Siljak" <alen.siljak at gmx.com>
>>> To: gnucash-user at gnucash.org
>>> Subject: Feedback for 2.7.2 on Windows
>>> Message-ID:
>>>
>>> <trinity-9a16ee0c-c366-4558-9548-154ed6b4555a-1511877196598 at 3c-app-mailcom-bs15>
>>>
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>>      Hi!
>>>
>>>      This is my first post to the list and I'm still figuring out where all
>>>      the different pieces of information should be addressed. I'm not sure
>>>      if there is a specific channel for the unstable version feedback,
>>> apart
>>>      from BugZilla.
>>>      I had a brief run of the 2.7.2 version of GnuCash on Windows 10. It
>>>      took a while to start the first time but everything went well there.
>>>      The application seems quicker and more responsive than 2.6.18 in
>>>      general.
>>>      One thing I noticed, though, is that no custom reports were available
>>>      in the Reports menu even though the settings were correctly copied to
>>>      the new location in the roaming profile folder.
>>>
>>>      Other than that, I'd like to thank you very much for this software
>>>      package. I've followed it for years but have only made the switch
>>>      recently. I'm still in the process of migrating the data. I really
>>> like
>>>      being able to run my own reports on the data and, in that regard, I
>>>      hope for more extensibility in the future. Python bindings are a great
>>>      idea but they are currrently not available on Windows.
>>>      Fortunately, Sebastien provided some wonderful functionality for
>>> Python
>>>      in the form of piecash and gnucash-utilities project. I'm writing some
>>>      portfolio tools and reports that I find missing in GnuCash, on top of
>>>      those two projects, in https://github.com/MisterY/gnucash-portfolio.
>>>      We'll see what this grows into and/if these get merged.
>>>
>>>      Cheers,
>>>
>>>      Alen
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 4
>>> Date: Tue, 28 Nov 2017 06:50:59 -0800
>>> From: John Ralls <jralls at ceridwen.us>
>>> To: Patrick Alken <alken at colorado.edu>
>>> Cc: gnucash-user at gnucash.org
>>> Subject: Re: Alphavantage not working in gnucash 2.6.17
>>> Message-ID: <73BA756E-A53D-48C7-8A3B-B7A9E26EC127 at ceridwen.us>
>>> Content-Type: text/plain;       charset=us-ascii
>>>
>>>
>>>
>>>> On Nov 27, 2017, at 9:57 PM, Patrick Alken <alken at colorado.edu> wrote:
>>>>
>>>> Apologies if this has already been asked, but I couldn't find this exact
>>>> issue in the recent mailings.
>>>>
>>>> I have:
>>>>
>>>> gnucash: 2.6.17
>>>>
>>>> F::Q: 1.47
>>>>
>>>> My F::Q works from the command line:
>>>>
>>>> ----------
>>>>
>>>> $ gnc-fq-dump alphavantage CSCO
>>>> Finance::Quote fields Gnucash uses:
>>>>       symbol: CSCO                 <=== required
>>>>         date: 11/27/2017           <=== recommended
>>>>     currency: USD                  <=== required
>>>>         last: 36.8700              <=\
>>>>          nav:                      <=== one of these
>>>>        price:                      <=/
>>>>     timezone:                      <=== optional
>>>> ----------
>>>>
>>>> However inside gnucash price editor I still get the "unknown error when
>>>> retrieving price quotes".
>>>>
>>>> I have unchecked the "Get Online Quotes" flag from ALL of my stocks in
>>>> the security editor. However the price editor still gives me the same
>>>> error (unknown error).
>>>>
>>>> gnucash --debug shows nothing related to quotes. I only get lines like
>>>> this:
>>>>
>>>> ----
>>>>
>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>> baln=0/1
>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>> baln=0/100
>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>> baln=0/100
>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>> baln=0/100
>>>>
>>>> ----
>>>>
>>>> Can anyone advise how to diagnose the issue?
>>> What OS and how did you install F::Q?
>>>
>>> Regards,
>>> John Ralls
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 5
>>> Date: Tue, 28 Nov 2017 10:10:21 -0500
>>> From: Fiona Vella <fmcvella at gmail.com>
>>> To: gnucash-user at gnucash.org
>>> Subject: MacOS Sierra - Upgrade Problems
>>> Message-ID:
>>>
>>> <CA+5H=D99W0e5-xGEPwR+A2zDXzVyDd5P_0Q461h3YiH29vXORQ at mail.gmail.com>
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> Hello all,
>>>
>>> I recently upgraded to MacOS High Sierra and now the Gnucash application
>>> will no longer open. Have others experienced this problem elsewhere? Is
>>> there a fix?
>>>
>>> Thanks in advance.
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 6
>>> Date: Tue, 28 Nov 2017 07:27:55 -0800
>>> From: Alan Whiteman <a.c.whiteman at gmail.com>
>>> To: gnucash-user at gnucash.org
>>> Subject: Re: GnuCash release numbering
>>> Message-ID: <a38ea0ca-8b70-7a80-7a87-9a7dd9663fb2 at gmail.com>
>>> Content-Type: text/plain; charset=utf-8; format=flowed
>>>
>>> Thank you Eric for such a thorough explanation. Very nice.
>>>
>>> I think my point is purely from a marketing perspective. For the
>>> number-inclined people such as accountants and software developers, this
>>> all makes perfect sense. However, for the ordinary folk the system can
>>> be confusing. So perhaps a sort of "cosmetic" version system may be
>>> employed?
>>>
>>> 2.6.18 -> "Version 26"
>>>
>>> 2.7.0 -> "Version 27"
>>>
>>> 2.7.1 -> Version 28"
>>>
>>> ...etc.
>>>
>>> Although to be perfectly honest, "stable release" is clearly labeled on
>>> the website.
>>>
>>> On 11/27/2017 07:59 PM, Eric Siegerman wrote:
>>>> On Tue, Nov 21, 2017 at 02:14:31PM -0500, davelist at mac.com wrote:
>>>>> Yes, 2.6.18 is newer. Each number between the periods is a
>>>>> separate number and 18 is greater than 3.
>>>> To expand on that:  software version numbers don't work like
>>>> decimal fractions, even though they use "." as a separator.
>>>> Think of "2.6.18" as a series of (multi-digit) integers, and
>>>> compare each integer in turn until you find one that differs:
>>>>         2 = 2
>>>>         6 = 6
>>>>        18 > 3    <--- Bingo!
>>>>
>>>> To put it another way: unlike in mathematics, "2.6.3" and
>>>> "2.6.30" are *not* equal.  (GnuCash 2.6.30 doesn't exist -- nor,
>>>> I imagine, will it ever exist, because the whole 2.6.x series
>>>> will reach end-of-life long before it gets twelve more releases.)
>>>>
>>>> It gets weirder; I oversimplified, above.  The individual
>>>> components of a version number are not always integers.  There
>>>> can be other characters as well, usually letters.  Worse, what
>>>> those letters mean depends on the project.
>>>>
>>>> In some projects, "3a" comes before "3".  To invent an example,
>>>> "4.7.3a1" might be the first "alpha testing" pre-release.  Then
>>>> "beta" releases like 4.7.3b1; then "release candidates" like
>>>> 4.7.3rc1; and finally the *real* release, 4.7.3 itself.
>>>>
>>>> In other projects, it's the other way around -- something like
>>>> "3a" comes *after* "3".
>>>>
>>>> GnuCash works the second way.  It had 2.6.17a and 2.6.17b as
>>>> *very* minor post-release corrections to 2.6.17.  Typically
>>>> one tries to avoid needing these post-release fixups, and in
>>>> fact GnuCash 2.6.18 hasn't needed any ... but sometimes stuff
>>>> happens...
>>>>
>>>> One wants the world of computers to be as logical as Mr. Spock,
>>>> but alas, we humans seem able to make a confusing mess out of
>>>> anything :-/
>>>>
>>>>> In general, do not download the 2.7.x versions as those are
>>>>> beta releases for the next version unless you are testing those
>>>>> with other data (i.e., don't run a 2.7 with the only copy of
>>>>> your actual data file).
>>>> The way GnuCash distinguishes testing prereleases is with odd vs.
>>>> even numbers for the second component.  The 2.6.x series are
>>>> "stable", i.e. intended for production use.  There are already
>>>> several 2.7.x releases, but those are "unstable"; they're only
>>>> for testing, *not* production use.  Once the 2.7.x series
>>>> stabilizes, they'll release 2.8.0, which will be the first stable
>>>> release of the new series.  So:
>>>>
>>>>        2.6.3     <--- Several years old now
>>>>        ...
>>>>        2.6.16
>>>>        2.6.17
>>>>        2.6.17a
>>>>        2.6.17b
>>>>        2.6.18    <--- The current stable release.  INSTALL THIS ONE.
>>>>
>>>>        2.7.0     \    These already exist ...
>>>>        2.7.1     |    ... but they're for testing only.
>>>>        2.7.2     /    DO NOT USE them for real work!
>>>>
>>>> ------------  <--- (2017-11-27.  Below here is in the future.)
>>>>
>>>>        2.6.19    <--- The next stable release in the 2.6.x series
>>>>        2.7.3     <--- The next testing release
>>>>        2.6.x     <--- Repeat as necessary ...
>>>>        2.7.y     <--- ... until ...
>>>>
>>>>        2.8.0     <--- The first stable release of the new series
>>>>        2.8.1     <--- And so on
>>>>        ...
>>>>        2.9.0     <--- First of the testing prereleases leading up to
>>>>                       2.10.0
>>>>
>>>>
>>>>      - Eric
>>>> _______________________________________________
>>>> 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.
>>>>
>>>
>>> ------------------------------
>>>
>>> Message: 7
>>> Date: Tue, 28 Nov 2017 09:28:09 -0600
>>> From: Gerry Starnes <gerrystarnes at gmail.com>
>>> To: Fiona Vella <fmcvella at gmail.com>
>>> Cc: Gnucash User List <gnucash-user at gnucash.org>
>>> Subject: Re: MacOS Sierra - Upgrade Problems
>>> Message-ID:
>>>
>>> <CAK8D83frw-esdGyPBRnttUDw-D5EAwqZt2kBhp2p3xJ6M7sV_Q at mail.gmail.com>
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> Yes. Upgraded to latest version. Problem solved.
>>>
>>> GS
>>>
>>>
>>> On Tue, Nov 28, 2017 at 9:10 AM, Fiona Vella <fmcvella at gmail.com> wrote:
>>>
>>>> Hello all,
>>>>
>>>> I recently upgraded to MacOS High Sierra and now the Gnucash application
>>>> will no longer open. Have others experienced this problem elsewhere? Is
>>>> there a fix?
>>>>
>>>> Thanks in advance.
>>>> _______________________________________________
>>>> 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.
>>>>
>>> ------------------------------
>>>
>>> Message: 8
>>> Date: Tue, 28 Nov 2017 16:29:30 +0100
>>> From: Christoph R <subscriptions+listen at rohland.net>
>>> To: Fiona Vella <fmcvella at gmail.com>
>>> Cc: gnucash-user at gnucash.org
>>> Subject: Re: MacOS Sierra - Upgrade Problems
>>> Message-ID: <9B3EBD4A-C40C-4CD7-BD14-C2CB03B2266C at rohland.net>
>>> Content-Type: text/plain;       charset=us-ascii
>>>
>>> Hi Fiona,
>>>
>>> upgrade to the latest version (2.6.18) from http://www.gnucash.org
>>>
>>> Cheers,
>>> Christoph
>>>
>>>> Am 28.11.2017 um 16:10 schrieb Fiona Vella <fmcvella at gmail.com>:
>>>>
>>>> Hello all,
>>>>
>>>> I recently upgraded to MacOS High Sierra and now the Gnucash application
>>>> will no longer open. Have others experienced this problem elsewhere? Is
>>>> there a fix?
>>>>
>>>> Thanks in advance.
>>>> _______________________________________________
>>>> 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.
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 9
>>> Date: Tue, 28 Nov 2017 10:35:20 -0500
>>> From: Fiona Vella <fmcvella at gmail.com>
>>> To: Christoph R <subscriptions+listen at rohland.net>
>>> Cc: gnucash-user at gnucash.org
>>> Subject: Re: MacOS Sierra - Upgrade Problems
>>> Message-ID: <9A0A5CF2-2719-471A-8CF9-3D9DD961905D at gmail.com>
>>> Content-Type: text/plain;       charset=us-ascii
>>>
>>> Thanks all!
>>>
>>>> On Nov 28, 2017, at 10:29 AM, Christoph R
>>>> <subscriptions+listen at rohland.net> wrote:
>>>>
>>>> Hi Fiona,
>>>>
>>>> upgrade to the latest version (2.6.18) from http://www.gnucash.org
>>>>
>>>> Cheers,
>>>> Christoph
>>>>
>>>>> Am 28.11.2017 um 16:10 schrieb Fiona Vella <fmcvella at gmail.com>:
>>>>>
>>>>> Hello all,
>>>>>
>>>>> I recently upgraded to MacOS High Sierra and now the Gnucash application
>>>>> will no longer open. Have others experienced this problem elsewhere? Is
>>>>> there a fix?
>>>>>
>>>>> Thanks in advance.
>>>>> _______________________________________________
>>>>> 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.
>>>
>>> ------------------------------
>>>
>>> Message: 10
>>> Date: Tue, 28 Nov 2017 09:46:25 -0700
>>> From: Patrick Alken <alken at colorado.edu>
>>> To: John Ralls <jralls at ceridwen.us>
>>> Cc: gnucash-user at gnucash.org
>>> Subject: Re: Alphavantage not working in gnucash 2.6.17
>>> Message-ID: <ed793588-bd39-84a0-dcc4-6ce244c99a28 at colorado.edu>
>>> Content-Type: text/plain; charset=utf-8; format=flowed
>>>
>>> My OS is Ubuntu linux 17.10
>>>
>>> and I installed F::Q via CPAN (gnc-fq-dump and gnc-fq-helper work ok
>>> from the commandline with alphavantage)
>>>
>>> On 11/28/2017 07:50 AM, John Ralls wrote:
>>>>> On Nov 27, 2017, at 9:57 PM, Patrick Alken <alken at colorado.edu> wrote:
>>>>>
>>>>> Apologies if this has already been asked, but I couldn't find this exact
>>>>> issue in the recent mailings.
>>>>>
>>>>> I have:
>>>>>
>>>>> gnucash: 2.6.17
>>>>>
>>>>> F::Q: 1.47
>>>>>
>>>>> My F::Q works from the command line:
>>>>>
>>>>> ----------
>>>>>
>>>>> $ gnc-fq-dump alphavantage CSCO
>>>>> Finance::Quote fields Gnucash uses:
>>>>>        symbol: CSCO                 <=== required
>>>>>          date: 11/27/2017           <=== recommended
>>>>>      currency: USD                  <=== required
>>>>>          last: 36.8700              <=\
>>>>>           nav:                      <=== one of these
>>>>>         price:                      <=/
>>>>>      timezone:                      <=== optional
>>>>> ----------
>>>>>
>>>>> However inside gnucash price editor I still get the "unknown error when
>>>>> retrieving price quotes".
>>>>>
>>>>> I have unchecked the "Get Online Quotes" flag from ALL of my stocks in
>>>>> the security editor. However the price editor still gives me the same
>>>>> error (unknown error).
>>>>>
>>>>> gnucash --debug shows nothing related to quotes. I only get lines like
>>>>> this:
>>>>>
>>>>> ----
>>>>>
>>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>>> baln=0/1
>>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>>> baln=0/100
>>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>>> baln=0/100
>>>>> * 22:34:53  INFO <gnc.account> [xaccAccountGetBalanceInCurrency]
>>>>> baln=0/100
>>>>>
>>>>> ----
>>>>>
>>>>> Can anyone advise how to diagnose the issue?
>>>> What OS and how did you install F::Q?
>>>>
>>>> Regards,
>>>> John Ralls
>>>>
>>>
>>> ------------------------------
>>>
>>> Message: 11
>>> Date: Tue, 28 Nov 2017 10:53:32 -0600
>>> From: Steve Goings <jsgoings at novagraph.com>
>>> To: gnucash-user at gnucash.org
>>> Subject: Slow startup on Windows 10, v2.6.18
>>> Message-ID:
>>>
>>> <CAOccJfgNRvzRZie4p2VEGmWK9m7_nBhK2WT9Y21+xZtd2i_BjA at mail.gmail.com>
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> I've been using 2.6.18 on Windows 10 for some weeks with no problems until
>>> recently.
>>>
>>> Now, startup gets very slow as Gnucash renders the first report that was
>>> displayed in the last session. It takes about 30 seconds to render that
>>> first report. Then the other reports render quickly, as expected.
>>>
>>> When I close all the reports and then close Gnucash, restart happens
>>> quickly as expected. Then when I try to run any report, there is again
>>> about a 30 second delay to render that first report, no matter what it is.
>>> After that, other reports are rendered quickly.
>>>
>>> I have created a new Gnucash file, with the basic accounts, and no data,
>>> and get the same delay when rendering any of the standard reports the
>>> first
>>> time.
>>>
>>> I have removed and reinstalled Gnucash 2.6.18, to no avail. When I look at
>>> the Windows task manager, nothing seems to be eating CPU cycles or doing
>>> anything to slow down the system.
>>>
>>> I also have the latest Mac version of Gnucash running on a MacBook Pro,
>>> and
>>> it does not have this problem on the same data file and reports.
>>>
>>> Seeing this long delay after seeing none earlier has made me worry about
>>> some problem in the installation on Windows. I have tried clearing out all
>>> the Gnucash support files, such as I can find and reinstalling. None of
>>> this helps.
>>>
>>> Is this long delay on Windows for the first report rendering expected
>>> behavior now? If anyone has some ideas I would be grateful.
>>>
>>> In the meantime, I have gone back to 2.4.15 on Windows, and it works
>>> without any of the delays, but I would prefer to use the newer release if
>>> possible.
>>>
>>> I tried the development release, and it would not even run on my system.
>>>
>>> Thanks in advance for any advice or suggestions. I did report a bug on
>>> this,
>>>
>>> SG
>>>
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> _______________________________________________
>>> gnucash-user mailing list
>>> gnucash-user at gnucash.org
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>>
>>>
>>> ------------------------------
>>>
>>> End of gnucash-user Digest, Vol 176, Issue 58
>>> *********************************************
>>>
>> _______________________________________________
>> 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.



More information about the gnucash-user mailing list