Re: [GNC] Multi currency income

[David Cousens]

Hi JB,

I have just duplicated the transaction you described of crediting a USD
account and debiting it  an AUD account and it worked fine as I would
expect, not creating any additional accounts and using the current exchange
rate for USD->AUD which it fetched. screenshots attached. GnuCash 3.4 on
Linux Mint 19

test10-Shareholder_USD-GnuCash_001.png

  

test10-Shareholder_USD-GnuCash_001.png

  

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@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.

[GNC] Updating From V 2.6.11

[Rick & Janelle Halvorson]

I am currently using version 2.6.11. I want to update to the most recent 
version to take advantage of the reconciliation report addition. How do I do 
that, and where is the download for the latest version found? 


Do I just install the latest version "over the top" of V2.6.11? 
Is there an update to install? 
Do I delete (uninstall) V2.6.11 and reinstall? If so, what do I need to save to 
recover my existing data? 


Thank you! I love using the software! 


Rick Halvorson 

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Colin Law]

On a Mac is it possible to open a second instance of GC while one is
still running?  If so another possibility is that you did not save and
close the first instance so it was still open when you started GC
again?  Then you would get the lock message and would find that the
reconcile had not been saved.  On the other hand the original one
would still have been lying around, so I would have thought you would
have noticed that at some point.

Colin

On Fri, 8 Feb 2019 at 04:22, John Ralls  wrote:
>
> That means that it didn't actually crash, it quit "normally" where "normally" 
> is what the OS thinks is normal, not necessarily what the rest of us do.
>
> Regards,
> John Ralls
>
>
> > On Feb 7, 2019, at 4:40 PM, Michael Hendry  wrote:
> >
> >> On 7 Feb 2019, at 17:22, John Ralls  wrote:
> >>
> >>
> >>
> >>> On Feb 7, 2019, at 12:52 AM, Colin Law  wrote:
> >>>
> >>> On Thu, 7 Feb 2019 at 07:37, Michael Hendry 
> >>> wrote:
> >>>
> > On 3 Feb 2019, at 14:59, Jamestk  wrote:
> >
> > Ira me again, this seems to be happening on v3.4
> >
> > Changes made by ticking entries are no longer saved after opting to
> > postpone, anyone else noticed this?
> 
> 
>  A slightly different (but perhaps connected?) reconciliation problem
>  happened to me yesterday.
> 
>  I’m using version 3.4 on iMac with High Sierra.
> 
>  I reconciled 9 separate statements with their corresponding accounts on
>  Tuesday. In some instances I had to enter transactions which appeared on
>  the statement but for which I didn’t have a receipt (e.g. contactless
>  travel charges), and found I couldn’t do this without postponing (this is
>  possible in 2.6.16). Once I’d made these entries I was able to go back 
>  and
>  complete the reconciliation.
> 
>  Yesterday morning I reconciled a single account, marked it complete,
>  clicked “Save” and quit Gnucash - I was going to be out all day, and 
>  wasn’t
>  planning to do any more work on the books. The unusual aspect was the 
>  quick
>  sequence of finishing the reconciliation, clicking Save and Quit - 
>  usually
>  I would tidy up the papers before shutting down. The Mac itself was left
>  running.
> 
>  In the evening I decided to reconcile another couple of statements, but
>  when I started Gnucash I got the lock-file warning, but overrode it 
>  because
>  there was no other instance of Gnucash running, only to find that the
>  reconciliation from the morning hadn’t been saved.
> 
>  A number of minor corrections I’d made to transactions during the session
>  have been recorded.
> 
>  I suppose it’s possible that I hit Cancel instead of Finish at the end of
>  the reconciliation, but I’ve never made this error since I started using 
>  GC
>  in 2010.
> 
> >>>
> >>> I think it more  likely that is a different issue, it sounds more as if GC
> >>> crashed for some reason so had not saved the data.
> >>
> >> Right, and if so there should be a crash report in 
> >> /Applications/Utilities/Console.
> >>
> >> Regards,
> >> John Ralls
> >
> > Can’t find one related to this problem, but did find an earlier one 
> > relating to the failure of 2.6.3 (before you fixed it, John), which would 
> > suggest that I’m looking in the right place.
> >
> > The first 20-odd lines of that report follow.
> >
> > Michael
> >
> >
> > Process:   Gnucash-bin [10851]
> > Path:  /Applications/Gnucash2.6.3.app/Contents/MacOS/Gnucash
> > Identifier:org.gnucash.Gnucash
> > Version:   ???
> > Code Type: X86 (Native)
> > Parent Process:??? [1]
> > Responsible:   Gnucash-bin [10851]
> > User ID:   501
> >
> > Date/Time: 2019-01-29 11:28:05.325 +
> > OS Version:Mac OS X 10.13.6 (17G4015)
> > Report Version:12
> > Anonymous UUID:6E4C0EFC-2FF3-6AA3-4C59-DBC3DB6D08BC
> >
> > Sleep/Wake UUID:   7C6A5C36-4914-4581-8EAD-7280B55B0DF1
> >
> > Time Awake Since Boot: 14 seconds
> > Time Since Wake:   92000 seconds
> >
> > System Integrity Protection: enabled
> >
> > Crashed Thread:0
> >
> > Exception Type:EXC_CRASH (SIGABRT)
> > Exception Codes:   0x, 0x
> > Exception Note:EXC_CORPSE_NOTIFY
> >
> > Termination Reason:DYLD, [0x4] Symbol missing
> >
>
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] Updating From V 2.6.11

[Colin Law]

To know the answer it would be helpful to know which operating system
you are using and how you installed it in the first place.

Colin

On Fri, 8 Feb 2019 at 08:08, Rick & Janelle Halvorson
 wrote:
>
> I am currently using version 2.6.11. I want to update to the most recent 
> version to take advantage of the reconciliation report addition. How do I do 
> that, and where is the download for the latest version found?
>
>
> Do I just install the latest version "over the top" of V2.6.11?
> Is there an update to install?
> Do I delete (uninstall) V2.6.11 and reinstall? If so, what do I need to save 
> to recover my existing data?
>
>
> Thank you! I love using the software!
>
>
> Rick Halvorson
>
> ___
> gnucash-user mailing list
> gnucash-user@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@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.

Re: [GNC] Debian Files for GnuCash 3.4-x

[Colin Law]

On Thu, 7 Feb 2019 at 22:18, Stephen M. Butler  wrote:
> ...
> Should work on any distro that will accept a *.deb package file. Note
> the operative word here is "should".

That's interesting, I assumed it would have to have built in
dependencies on particular packages.  Has anyone tried them on Ubuntu
16.04?

If I run
apt-cache depends gnucash
it shows the list of packages that need to be installed to make it go.
This includes, for example, libboost-date-time1.65.1, I would have
expected the install to fail if the distribution does not have that
package available.  I may be wrong here though, I am a bit out of my
comfort zone.

Colin
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 08:38, Colin Law  wrote:
> 
> On a Mac is it possible to open a second instance of GC while one is
> still running?  

Yes, but opening the second instance brings up the lock file warning, and this 
is the first time I’ve seen that warning in many weeks.

It usually happens after a power cut, or when I’ve had to power down the 
computer without an orderly shutdown.

> If so another possibility is that you did not save and
> close the first instance so it was still open when you started GC
> again?

…so I don’t think that’s the problem.


>  Then you would get the lock message and would find that the
> reconcile had not been saved.  On the other hand the original one
> would still have been lying around, so I would have thought you would
> have noticed that at some point.
> 
> Colin

What was unusual about the work that preceded this incident was that I clicked 
“Save” and then promptly shut Gnucash down - I usually find that when I come to 
quit Gnucash the “Save” button is already greyed, indicating that an auto-save 
has already taken place.

Michael

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[David T. via gnucash-user]

I know that on my Mac, it takes some time for gnucash to actually finish the 
save process.  Mine is a somewhat older macbook pro with an SSD. Is it possible 
that you failed to wait for it to finish saving?
David T.
 
 
  On Fri, Feb 8, 2019 at 14:23, Michael Hendry wrote: 
  > On 8 Feb 2019, at 08:38, Colin Law  wrote:
> 
> On a Mac is it possible to open a second instance of GC while one is
> still running?  

Yes, but opening the second instance brings up the lock file warning, and this 
is the first time I’ve seen that warning in many weeks.

It usually happens after a power cut, or when I’ve had to power down the 
computer without an orderly shutdown.

> If so another possibility is that you did not save and
> close the first instance so it was still open when you started GC
> again?

…so I don’t think that’s the problem.


>  Then you would get the lock message and would find that the
> reconcile had not been saved.  On the other hand the original one
> would still have been lying around, so I would have thought you would
> have noticed that at some point.
> 
> Colin

What was unusual about the work that preceded this incident was that I clicked 
“Save” and then promptly shut Gnucash down - I usually find that when I come to 
quit Gnucash the “Save” button is already greyed, indicating that an auto-save 
has already taken place.
Michael

___
gnucash-user mailing list
gnucash-user@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@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.

Re: [GNC] I just need a line feed

[Geert Janssens]

Op donderdag 7 februari 2019 23:15:18 CET schreef David Carlson:
> I am faced with inserting linefeeds into OFX files at certain critical
> locations to make them more palatable to libofx.  In that context I have
> found that I can open them with LibreOffice, turn on Formatting Marks (Ctrl
> F10) then place the curser wherever I want a linefeed and press
> Shift-Enter.  Last, I need to be sure to save the file with a modified
> filename but the original suffix in text-only format.
> 
> That is working for me.  Of course the linefeeds do need to be correctly
> placed for the application.

That's a completely different story :)

The OFX parser is not an html parser, though both are based on SGML in one way 
or another. And the OFX parser has a bug causing it to misinterpret certain 
tags. By sheer luck the bug is not triggered if that tag is on a line of its 
own.

However the html parser has no bug. Html be definition ignores newlines in 
textual data. The "\n" people refer to here is just a coder's representation 
of that newline. So the html parser will ignore it.

In this case Derek offered the proper solution: use  instead.

Regards,

Geert


___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Colin Law]

On Fri, 8 Feb 2019 at 09:25, David T.  wrote:
>
> I know that on my Mac, it takes some time for gnucash to actually finish the 
> save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
> possible that you failed to wait for it to finish saving?

I think it should not be possible to shutdown after clicking Save but
before it has finished saving.  If that is possible then that suggests
a bug.  That possibility would appear to fit many of the facts the
however.

Colin

>
> David T.
>
>
> On Fri, Feb 8, 2019 at 14:23, Michael Hendry
>  wrote:
> > On 8 Feb 2019, at 08:38, Colin Law  wrote:
> >
> > On a Mac is it possible to open a second instance of GC while one is
> > still running?
>
> Yes, but opening the second instance brings up the lock file warning, and 
> this is the first time I’ve seen that warning in many weeks.
>
> It usually happens after a power cut, or when I’ve had to power down the 
> computer without an orderly shutdown.
>
> > If so another possibility is that you did not save and
> > close the first instance so it was still open when you started GC
> > again?
>
> …so I don’t think that’s the problem.
>
>
> >  Then you would get the lock message and would find that the
> > reconcile had not been saved.  On the other hand the original one
> > would still have been lying around, so I would have thought you would
> > have noticed that at some point.
> >
> > Colin
>
> What was unusual about the work that preceded this incident was that I 
> clicked “Save” and then promptly shut Gnucash down - I usually find that when 
> I come to quit Gnucash the “Save” button is already greyed, indicating that 
> an auto-save has already taken place.
>
> Michael
>
> ___
> gnucash-user mailing list
> gnucash-user@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@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 09:25, David T.  wrote:
> 
> I know that on my Mac, it takes some time for gnucash to actually finish the 
> save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
> possible that you failed to wait for it to finish saving?
> 
> David T.

That’s what I was implying, although I would be surprised if Gnucash didn’t 
have a means of preventing itself from being shut down while busy doing a file 
save.

In any case, the orderly shutting down of the program (i.e. not involving a 
crash) should have included the deletion of the lock file even if it had 
abandoned the “Save”.

Michael

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 10:02, Michael Hendry  wrote:
> 
>> On 8 Feb 2019, at 09:25, David T.  wrote:
>> 
>> I know that on my Mac, it takes some time for gnucash to actually finish the 
>> save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
>> possible that you failed to wait for it to finish saving?
>> 
>> David T.
> 
> That’s what I was implying, although I would be surprised if Gnucash didn’t 
> have a means of preventing itself from being shut down while busy doing a 
> file save.
> 
> In any case, the orderly shutting down of the program (i.e. not involving a 
> crash) should have included the deletion of the lock file even if it had 
> abandoned the “Save”.
> 
> Michael
> 

Further lock file problem:

Yesterday evening I completed the failed reconciliation, along with a few other 
transactions, and quit GC before going out for a few hours at 20:30.

Returning home around midnight, I opened my GC file again, and tidied up a 
couple of loose ends, and closed down shortly afterwards.

Today when I tried to run GC, I got the lock file message, and this time I 
clicked “Quit” rather than forcing the file open.

I checked with Activity Monitor that there was no current instance of GC 
running.

Here is a screenshot of the Accounts folder’s most recent files:

https://www.dropbox.com/s/zjvogbdl885rr2d/Screenshot%202019-02-08%2015.12.05.png?dl=0

and the same information via the command-line:

| => ls -lt
total 84324
-rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 MDH.gnucash.tmp-ea6yhc
-rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
MDH.gnucash.20190208000345.log
-rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.0.82823.LNK
-rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
-rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
MDH.gnucash.20190207202353.log
-rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
-rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
MDH.gnucash.20190207202200.log
-rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
MDH.gnucash.20190208000443.gnucash
-rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
MDH.gnucash.20190207185926.log
-rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
MDH.gnucash.20190207202348.gnucash
-rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
MDH.gnucash.20190207202153.gnucash

There is no corresponding crash report, so I conclude that GC has failed to 
tidy up properly before closing.

Michael

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

> On Feb 8, 2019, at 2:02 AM, Michael Hendry  wrote:
> 
>> On 8 Feb 2019, at 09:25, David T.  wrote:
>> 
>> I know that on my Mac, it takes some time for gnucash to actually finish the 
>> save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
>> possible that you failed to wait for it to finish saving?
>> 
>> David T.
> 
> That’s what I was implying, although I would be surprised if Gnucash didn’t 
> have a means of preventing itself from being shut down while busy doing a 
> file save.
> 
> In any case, the orderly shutting down of the program (i.e. not involving a 
> crash) should have included the deletion of the lock file even if it had 
> abandoned the “Save”.

Remember, I said "normal" isn't necessarily normal for the rest of us. It 
doesn't necessarily mean that GnuCash got to do an orderly shutdown. The most 
obvious reason is a force quit where the operating system just removes the 
process and reclaims its memory. GnuCash doesn't have a chance to respond--no 
NSAppWillTerminate notification--and if there's a save in process it's likely 
that the file will be trashed. The application itself or one of its 
dependencies can call exit() after detecting an error and that will stop 
everything, no questions asked. GnuCash itself doesn't have any code like that 
but Glib does. I think Gtk does. There are probably others, those are the only 
two dependencies the internals of which I have some familiarity.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

> On Feb 8, 2019, at 7:31 AM, Michael Hendry  wrote:
> 
>> On 8 Feb 2019, at 10:02, Michael Hendry  wrote:
>> 
>>> On 8 Feb 2019, at 09:25, David T.  wrote:
>>> 
>>> I know that on my Mac, it takes some time for gnucash to actually finish 
>>> the save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
>>> possible that you failed to wait for it to finish saving?
>>> 
>>> David T.
>> 
>> That’s what I was implying, although I would be surprised if Gnucash didn’t 
>> have a means of preventing itself from being shut down while busy doing a 
>> file save.
>> 
>> In any case, the orderly shutting down of the program (i.e. not involving a 
>> crash) should have included the deletion of the lock file even if it had 
>> abandoned the “Save”.
>> 
>> Michael
>> 
> 
> Further lock file problem:
> 
> Yesterday evening I completed the failed reconciliation, along with a few 
> other transactions, and quit GC before going out for a few hours at 20:30.
> 
> Returning home around midnight, I opened my GC file again, and tidied up a 
> couple of loose ends, and closed down shortly afterwards.
> 
> Today when I tried to run GC, I got the lock file message, and this time I 
> clicked “Quit” rather than forcing the file open.
> 
> I checked with Activity Monitor that there was no current instance of GC 
> running.
> 
> Here is a screenshot of the Accounts folder’s most recent files:
> 
> https://www.dropbox.com/s/zjvogbdl885rr2d/Screenshot%202019-02-08%2015.12.05.png?dl=0
> 
> and the same information via the command-line:
> 
> | => ls -lt
> total 84324
> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
> MDH.gnucash.tmp-ea6yhc
> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
> MDH.gnucash.20190208000345.log
> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
> MDH.gnucash.0.82823.LNK
> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
> MDH.gnucash.20190207202353.log
> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
> MDH.gnucash.20190207202200.log
> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
> MDH.gnucash.20190208000443.gnucash
> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
> MDH.gnucash.20190207185926.log
> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
> MDH.gnucash.20190207202348.gnucash
> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
> MDH.gnucash.20190207202153.gnucash
> 
> There is no corresponding crash report, so I conclude that GC has failed to 
> tidy up properly before closing.

Do you remember how you did the save last night? IOW did you click the save 
button, wait until the save was finished, and select GnuCash>Quit from the menu 
or type Cmd-Q and then select "Save before quitting" from the dialog box, or 
perhaps click the save icon and then immediately type Cmd-Q?

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 15:42, John Ralls  wrote:
> 
> 
> 
>> On Feb 8, 2019, at 7:31 AM, Michael Hendry  wrote:
>> 
>>> On 8 Feb 2019, at 10:02, Michael Hendry  wrote:
>>> 
 On 8 Feb 2019, at 09:25, David T.  wrote:
 
 I know that on my Mac, it takes some time for gnucash to actually finish 
 the save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
 possible that you failed to wait for it to finish saving?
 
 David T.
>>> 
>>> That’s what I was implying, although I would be surprised if Gnucash didn’t 
>>> have a means of preventing itself from being shut down while busy doing a 
>>> file save.
>>> 
>>> In any case, the orderly shutting down of the program (i.e. not involving a 
>>> crash) should have included the deletion of the lock file even if it had 
>>> abandoned the “Save”.
>>> 
>>> Michael
>>> 
>> 
>> Further lock file problem:
>> 
>> Yesterday evening I completed the failed reconciliation, along with a few 
>> other transactions, and quit GC before going out for a few hours at 20:30.
>> 
>> Returning home around midnight, I opened my GC file again, and tidied up a 
>> couple of loose ends, and closed down shortly afterwards.
>> 
>> Today when I tried to run GC, I got the lock file message, and this time I 
>> clicked “Quit” rather than forcing the file open.
>> 
>> I checked with Activity Monitor that there was no current instance of GC 
>> running.
>> 
>> Here is a screenshot of the Accounts folder’s most recent files:
>> 
>> https://www.dropbox.com/s/zjvogbdl885rr2d/Screenshot%202019-02-08%2015.12.05.png?dl=0
>> 
>> and the same information via the command-line:
>> 
>> | => ls -lt
>> total 84324
>> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
>> MDH.gnucash.tmp-ea6yhc
>> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
>> MDH.gnucash.20190208000345.log
>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
>> MDH.gnucash.0.82823.LNK
>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
>> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
>> MDH.gnucash.20190207202353.log
>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
>> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
>> MDH.gnucash.20190207202200.log
>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
>> MDH.gnucash.20190208000443.gnucash
>> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
>> MDH.gnucash.20190207185926.log
>> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
>> MDH.gnucash.20190207202348.gnucash
>> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
>> MDH.gnucash.20190207202153.gnucash
>> 
>> There is no corresponding crash report, so I conclude that GC has failed to 
>> tidy up properly before closing.
> 
> Do you remember how you did the save last night? IOW did you click the save 
> button, wait until the save was finished, and select GnuCash>Quit from the 
> menu or type Cmd-Q and then select "Save before quitting" from the dialog 
> box, or perhaps click the save icon and then immediately type Cmd-Q?
> 
> Regards,
> John Ralls

I clicked Save, waited for the save to finish and quit via Gnucash->Quit (i.e. 
not Cmd-Q).

Michael

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 15:42, John Ralls  wrote:
> 
> 
> 
>> On Feb 8, 2019, at 7:31 AM, Michael Hendry  wrote:
>> 
>>> On 8 Feb 2019, at 10:02, Michael Hendry  wrote:
>>> 
 On 8 Feb 2019, at 09:25, David T.  wrote:
 
 I know that on my Mac, it takes some time for gnucash to actually finish 
 the save process.  Mine is a somewhat older macbook pro with an SSD. Is it 
 possible that you failed to wait for it to finish saving?
 
 David T.
>>> 
>>> That’s what I was implying, although I would be surprised if Gnucash didn’t 
>>> have a means of preventing itself from being shut down while busy doing a 
>>> file save.
>>> 
>>> In any case, the orderly shutting down of the program (i.e. not involving a 
>>> crash) should have included the deletion of the lock file even if it had 
>>> abandoned the “Save”.
>>> 
>>> Michael
>>> 
>> 
>> Further lock file problem:
>> 
>> Yesterday evening I completed the failed reconciliation, along with a few 
>> other transactions, and quit GC before going out for a few hours at 20:30.
>> 
>> Returning home around midnight, I opened my GC file again, and tidied up a 
>> couple of loose ends, and closed down shortly afterwards.
>> 
>> Today when I tried to run GC, I got the lock file message, and this time I 
>> clicked “Quit” rather than forcing the file open.
>> 
>> I checked with Activity Monitor that there was no current instance of GC 
>> running.
>> 
>> Here is a screenshot of the Accounts folder’s most recent files:
>> 
>> https://www.dropbox.com/s/zjvogbdl885rr2d/Screenshot%202019-02-08%2015.12.05.png?dl=0
>> 
>> and the same information via the command-line:
>> 
>> | => ls -lt
>> total 84324
>> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
>> MDH.gnucash.tmp-ea6yhc
>> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
>> MDH.gnucash.20190208000345.log
>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
>> MDH.gnucash.0.82823.LNK
>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
>> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
>> MDH.gnucash.20190207202353.log
>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
>> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
>> MDH.gnucash.20190207202200.log
>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
>> MDH.gnucash.20190208000443.gnucash
>> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
>> MDH.gnucash.20190207185926.log
>> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
>> MDH.gnucash.20190207202348.gnucash
>> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
>> MDH.gnucash.20190207202153.gnucash
>> 
>> There is no corresponding crash report, so I conclude that GC has failed to 
>> tidy up properly before closing.
> 
> Do you remember how you did the save last night? IOW did you click the save 
> button, wait until the save was finished, and select GnuCash>Quit from the 
> menu or type Cmd-Q and then select "Save before quitting" from the dialog 
> box, or perhaps click the save icon and then immediately type Cmd-Q?
> 
> Regards,
> John Ralls

PS Looking at the log files, I’m reminded that a number of scheduled 
transactions took place during the session. Inspecting these it seems that each 
one is recorded four times - here’s an example extracted from the larger of the 
two log file:

= START
B   aefe075a22d466826d4735afb8159c08
cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +   
2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
Amazon Prime Subscription   n   0/1 
0/100   1970-01-01 01:00:00 +0100
B   aefe075a22d466826d4735afb8159c08
f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +   
2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
Amazon Prime Subscription   n   0/1 
0/100   1970-01-01 01:00:00 +0100
= END
= START
R   aefe075a22d466826d4735afb8159c08
cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +   
2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
Amazon Prime Subscription   n   0/1 
0/100   1970-01-01 01:00:00 +0100
R   aefe075a22d466826d4735afb8159c08
f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +   
2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
Amazon Prime Subscription   n   0/1 
0/100   1970-01-01 01:00:00 +0100
= END
= START
B   aefe075a22d466826d4735

Re: [GNC] postpone reconciliation broken: ignores my changes

[Colin Law]

On Fri, 8 Feb 2019 at 15:31, Michael Hendry 
wrote:> ...
> | => ls -lt
> total 84324
> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
> MDH.gnucash.tmp-ea6yhc
> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
> MDH.gnucash.20190208000345.log
> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
> MDH.gnucash.0.82823.LNK
> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
> MDH.gnucash.20190207202353.log
> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
> MDH.gnucash.20190207202200.log
> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
> MDH.gnucash.20190208000443.gnucash
> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
> MDH.gnucash.20190207185926.log
> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
> MDH.gnucash.20190207202348.gnucash
> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
> MDH.gnucash.20190207202153.gnucash
>
> There is no corresponding crash report, so I conclude that GC has failed to 
> tidy up properly before closing.

That looks odd.  Notice that the last successful save was 7 Feb 20:23.
Then it appears that GC was started at 8 Feb 00:03, a log file of 95k
bytes was created (which seems large) but the results of that work
were not saved.  I don't know, but it may be that the file
MDH.gnucash.tmp-ea6yhc is the result of the first half of the save
before it is compressed and the files renamed but I don't know.  How
you could get a log file that large in one minute I don't know.  I see
you have posted some of the contents and suggested they don't look
right.

Colin
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] [GNC-dev] Debian package

[John Griessen]

On 1/22/19 9:34 AM, Stephen M. Butler wrote:

Looks like the dependency list from the mainline is missing a few
entries.  I'll check that out.


I tested the package python3-gnucash_3.4-45-~0_amd64.deb
and could not install with debian testing:
 python3-gnucash depends on python3 (<< 3.7); however:
  Version of python3 on system is 3.7.2-1.

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

> On Feb 8, 2019, at 8:28 AM, Colin Law  wrote:
> 
> On Fri, 8 Feb 2019 at 15:31, Michael Hendry 
> wrote:> ...
>> | => ls -lt
>> total 84324
>> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
>> MDH.gnucash.tmp-ea6yhc
>> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
>> MDH.gnucash.20190208000345.log
>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
>> MDH.gnucash.0.82823.LNK
>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
>> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
>> MDH.gnucash.20190207202353.log
>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
>> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
>> MDH.gnucash.20190207202200.log
>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
>> MDH.gnucash.20190208000443.gnucash
>> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
>> MDH.gnucash.20190207185926.log
>> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
>> MDH.gnucash.20190207202348.gnucash
>> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
>> MDH.gnucash.20190207202153.gnucash
>> 
>> There is no corresponding crash report, so I conclude that GC has failed to 
>> tidy up properly before closing.
> 
> That looks odd.  Notice that the last successful save was 7 Feb 20:23.
> Then it appears that GC was started at 8 Feb 00:03, a log file of 95k
> bytes was created (which seems large) but the results of that work
> were not saved.  I don't know, but it may be that the file
> MDH.gnucash.tmp-ea6yhc is the result of the first half of the save
> before it is compressed and the files renamed but I don't know.  How
> you could get a log file that large in one minute I don't know.  I see
> you have posted some of the contents and suggested they don't look
> right.

Scheduled transactions is how he could get 95K of log file in milliseconds. 

Good eye, noticing the temp file: The save failed for some reason and left 
GnuCash in a state where it quit without removing the lock. It's too bad that 
we overwrite trace files on MacOS. It would be useful to see if anything got 
logged about the save failing.

I think it's time to open a bug on this.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

> On Feb 8, 2019, at 8:11 AM, Michael Hendry  wrote:
> 
> PS Looking at the log files, I’m reminded that a number of scheduled 
> transactions took place during the session. Inspecting these it seems that 
> each one is recorded four times - here’s an example extracted from the larger 
> of the two log file:
> 
> = START
> B aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> B aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> = END
> = START
> R aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> R aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> = END
> = START
> B aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> B aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> = END
> = START
> R aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> R aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +   
> 2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100   
> 9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63  
>   Amazon Prime Subscription   n   0/1 
> 0/100   1970-01-01 01:00:00 +0100
> = END
> 
> I don’t know what the significance of “B” and “R” is in the first column, but 
> the pairs of lines appear to be record the guids of the each transaction and 
> the accounts the split refers to. I don’t suppose the appearance of Unix zero 
> time (1970-01-01 01:00:00 +0100) at the end of each line is of any 
> significance.

There's a header at the top of the log file titling the columns. It's

"mod|trans_guid|split_guid|time_now|date_entered|date_posted|acc_guid|acc_name|num|description|notes|memo|action|reconciled|amount|value|date_reconciled"

The codes for the mod field are:

 'B' for 'begin edit' (followed by the transaction as it looks before any 
changes, i.e. the 'old value')
 'D' for delete (i.e. delete the previous B; echoes the data in the 'old B')
 'C' for commit (i.e. accept a previous B; data that follows is the 'new value')
 'R' for rollback (i.e. revert to previous B; data that follows should be 
identical to old B)

So GnuCash tried twice to create the two splits of the Amazon Prime 
Subscription transaction only to roll them back for some reason.

Regards,
John Ralls


___
gnucash-user mailing list
gnucash-user@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.
-

Re: [GNC] Debian Files for GnuCash 3.4-x

[Stephen M. Butler]

On 2/8/19 12:44 AM, Colin Law wrote:
> On Thu, 7 Feb 2019 at 22:18, Stephen M. Butler  wrote:
>> ...
>> Should work on any distro that will accept a *.deb package file. Note
>> the operative word here is "should".
> That's interesting, I assumed it would have to have built in
> dependencies on particular packages.  Has anyone tried them on Ubuntu
> 16.04?
>
> If I run
> apt-cache depends gnucash
> it shows the list of packages that need to be installed to make it go.
> This includes, for example, libboost-date-time1.65.1, I would have
> expected the install to fail if the distribution does not have that
> package available.  I may be wrong here though, I am a bit out of my
> comfort zone.
>
> Colin
>
I uninstalled gnucash and removed all "released" packages then did an
install on my box and it brought in all the dependent packages.

Here are my steps:

sudo apt remove gnucash gnucash-common python3-gnucash

sudo apt autoremove

sudo apt install ./*_3.4_*.deb

I've down this on Ubuntu 18.04 and have heard that it works on Ubuntu
18.10.  Let me know the results if you try it on Ubuntu 16.04.

Note:  If you built from scratch and installed that build, you may need
to do "sudo make uninstall" from the old build directory.

-- 
Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
---
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8


___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] Debian Files for GnuCash 3.4-x

[Ronal B Morse]

I downloaded the 3.4 release debs for testing with Ubuntu
18.10.  One can just double-click on the individual .debs and
the Ubuntu software installer will take care of the rest.
Install gnucash-common first as it is required by the main
program. I also installed the python .deb before the main
program, but I don't know if that makes any difference. 

I don't use the online transaction, price or quotes retrieval
functions so I don't know if those work. I haven't done much
with reports except to verify a balance sheet prints. Check
printing works. 

Testing was done with a data file I copied over from my
production machine that runs Gnucash 3.2-something.  No
apparent problems noted. 

Nice job, and thanks. 

Ron Morse. 


On Fri, 2019-02-08 at 10:34 -0800, Stephen M. Butler wrote:
> On 2/8/19 12:44 AM, Colin Law wrote:
> > On Thu, 7 Feb 2019 at 22:18, Stephen M. Butler <
> > kg...@arrl.net> wrote:
> > > ...
> > > Should work on any distro that will accept a *.deb
> > > package file. Note
> > > the operative word here is "should".
> > That's interesting, I assumed it would have to have built
> > in
> > dependencies on particular packages.  Has anyone tried
> > them on Ubuntu
> > 16.04?
> > 
> > If I run
> > apt-cache depends gnucash
> > it shows the list of packages that need to be installed
> > to make it go.
> > This includes, for example, libboost-date-time1.65.1, I
> > would have
> > expected the install to fail if the distribution does not
> > have that
> > package available.  I may be wrong here though, I am a
> > bit out of my
> > comfort zone.
> > 
> > Colin
> > 
> I uninstalled gnucash and removed all "released" packages
> then did an
> install on my box and it brought in all the dependent
> packages.
> 
> Here are my steps:
> 
> sudo apt remove gnucash gnucash-common python3-gnucash
> 
> sudo apt autoremove
> 
> sudo apt install ./*_3.4_*.deb
> 
> I've down this on Ubuntu 18.04 and have heard that it works
> on Ubuntu
> 18.10.  Let me know the results if you try it on Ubuntu
> 16.04.
> 
> Note:  If you built from scratch and installed that build,
> you may need
> to do "sudo make uninstall" from the old build directory.
> 

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[David Carlson]

If he hasn't deleted his backups yet he may be able to pick one before the
event and re-run the scheduled transactions.  Just a thought

David Carlson

On Fri, Feb 8, 2019 at 11:39 AM John Ralls  wrote:

>
>
> > On Feb 8, 2019, at 8:11 AM, Michael Hendry 
> wrote:
> >
> > PS Looking at the log files, I’m reminded that a number of scheduled
> transactions took place during the session. Inspecting these it seems that
> each one is recorded four times - here’s an example extracted from the
> larger of the two log file:
> >
> > = START
> > B aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > B aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > = END
> > = START
> > R aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > R aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > = END
> > = START
> > B aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > B aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > = END
> > = START
> > R aefe075a22d466826d4735afb8159c08
> cd4cb60c1e5a5294eb4e7d2623dbaebe2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > R aefe075a22d466826d4735afb8159c08
> f9d8cacc6b99135677ccc97ce6f4887d2019-02-08 00:03:46 +
>  2018-08-05 12:20:04 +0100   2018-08-05 11:59:00 +0100
>  9768413066e3e0d1272ba7839ea5f1ccb0e28c7d097d448b29f193895c973d63
>   Amazon Prime Subscription   n
>0/1 0/100   1970-01-01 01:00:00 +0100
> > = END
> >
> > I don’t know what the significance of “B” and “R” is in the first
> column, but the pairs of lines appear to be record the guids of the each
> transaction and the accounts the split refers to. I don’t suppose the
> appearance of Unix zero time (1970-01-01 01:00:00 +0100) at the end of each
> line is of any significance.
>
> There's a header at the top of the log file titling the columns. It's
>
>
> "mod|trans_guid|split_guid|time_now|date_entered|date_posted|acc_guid|acc_name|num|description|notes|memo|action|reconciled|amount|value|date_reconciled"
>
> The codes for the mod field are:
>
>  'B' for 'begin edit' (followed by the transaction as it looks before any
> changes, i.e. the 'old value')
>  'D' for delete (i.e. delete the previous B; echoes the data in the 'old
> B')
>  'C' for commit (i.e. accept a previous B; data that follows is the 'new
> value')
>  'R' for rollback (i.e. revert to previous B; data that follows should be
> identical to old B)
>
> So GnuCash tried twice to create the two splits of the Amazon Prime
> Subscription transaction only to roll them back for some reason.
>
> Regards,
> John Ralls
>
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or

Re: [GNC] postpone reconciliation broken: ignores my changes

[Jamestk]

Michael, just a thought - individual transactions should save after each
entry, tapping the return key will move onto the next one auto saving the
previous - the reconciliation process is likely to be somewhat different, 
GNC marks the entries but doesn't save these until the process is finalized
by activating 'finish' button, this will change entries from 'c' to 'r'
writing the result back to file - 

Could I ask what button is used when you mention 'marked as complete', if
its the green reconciled tick button this appears to be non functional?

Thanks,


"Yesterday morning I reconciled a single account, marked it complete,
clicked “Save” and quit Gnucash - I was going to be out all day, and wasn’t
planning to do any more work on the books. The unusual aspect was the quick
sequence of finishing the reconciliation, clicking Save and Quit - usually I
would tidy up the papers before shutting down. The Mac itself was left
running."





--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] Updating From V 2.6.11

[David Cousens]

Rick,

Windows installers usually uninstall previous versions as part of the
installation process. Can't be dead sure if that's the case for GnuCash as I
no longer use Windows.

On Linux, you normally have to uninstall a previous version before
installing the next version as some libraries may remain/not be overwritten
and cause problems if you don't. The Software Managerand or/apt can
uninstall (see the wiki for Gnucash Installation on Linux for uninstall
instructions depending on how it was installed).

On MacOS I don't know how it works.

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] Backup recovery

[David Cousens]

Finbar,

The directory with your data file will also contain log files  and backup
files.

See https://www.gnucash.org/docs/v3/C/gnucash-guide/basics-backup1.html for
details

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Colin Law]

On Fri, 8 Feb 2019 at 21:12, Jamestk  wrote:
>
> Michael, just a thought - individual transactions should save after each
> entry, tapping the return key will move onto the next one auto saving the
> previous - the reconciliation process is likely to be somewhat different,
> GNC marks the entries but doesn't save these until the process is finalized
> by activating 'finish' button, this will change entries from 'c' to 'r'
> writing the result back to file -
>
> Could I ask what button is used when you mention 'marked as complete', if
> its the green reconciled tick button this appears to be non functional?

The above is not correct except when using one of the database
backends.  With the default xml file it only saves when asked to do so
or every five minutes (or whatever) if the auto save interval is
configured.  It does not save after each transaction and the
completion of reconcile does not trigger a save.

Colin
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 17:26, John Ralls  wrote:
> 
> 
> 
>> On Feb 8, 2019, at 8:28 AM, Colin Law  wrote:
>> 
>> On Fri, 8 Feb 2019 at 15:31, Michael Hendry 
>> wrote:> ...
>>> | => ls -lt
>>> total 84324
>>> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
>>> MDH.gnucash.tmp-ea6yhc
>>> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
>>> MDH.gnucash.20190208000345.log
>>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
>>> MDH.gnucash.0.82823.LNK
>>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
>>> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
>>> MDH.gnucash.20190207202353.log
>>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
>>> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
>>> MDH.gnucash.20190207202200.log
>>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
>>> MDH.gnucash.20190208000443.gnucash
>>> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
>>> MDH.gnucash.20190207185926.log
>>> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
>>> MDH.gnucash.20190207202348.gnucash
>>> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
>>> MDH.gnucash.20190207202153.gnucash
>>> 
>>> There is no corresponding crash report, so I conclude that GC has failed to 
>>> tidy up properly before closing.
>> 
>> That looks odd.  Notice that the last successful save was 7 Feb 20:23.
>> Then it appears that GC was started at 8 Feb 00:03, a log file of 95k

Actually, the first file was modified on 8th Feb at 00:01, followed by the lock 
file at 00:03.

The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I suspect 
that it’s part of the compression process that eventually results in a new 
MDH.gnucash file.

>> bytes was created (which seems large) but the results of that work
>> were not saved.  I don't know, but it may be that the file
>> MDH.gnucash.tmp-ea6yhc is the result of the first half of the save
>> before it is compressed and the files renamed but I don't know.  How
>> you could get a log file that large in one minute I don't know.  I see
>> you have posted some of the contents and suggested they don't look
>> right.
> 
> Scheduled transactions is how he could get 95K of log file in milliseconds. 
> 
> Good eye, noticing the temp file: The save failed for some reason and left 
> GnuCash in a state where it quit without removing the lock. It's too bad that 
> we overwrite trace files on MacOS. It would be useful to see if anything got 
> logged about the save failing.
> 
> I think it's time to open a bug on this.
> 
> Regards,
> John Ralls

Thanks, John.

Is it up to me to initiate this? 

Michael
___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Colin Law]

Actually there seems to be something similarly odd going on with my
3.4 system on Ubuntu.  When I open GC it immediately creates a 90k log
file with loads of scheduled transaction entries, none of which do (or
should) actually make it to the register.  So for instance I see
= START
B4edff70199ce6659c8739ee541adb772
aeb2ee83f309c966cbb9fb8c9d92e6f52019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
B4edff70199ce6659c8739ee541adb772
29942dc723b0c19cd47c078e62811a3e2019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
= END
= START
R4edff70199ce6659c8739ee541adb772
aeb2ee83f309c966cbb9fb8c9d92e6f52019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
R4edff70199ce6659c8739ee541adb772
29942dc723b0c19cd47c078e62811a3e2019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
= END
= START
B4edff70199ce6659c8739ee541adb772
aeb2ee83f309c966cbb9fb8c9d92e6f52019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
B4edff70199ce6659c8739ee541adb772
29942dc723b0c19cd47c078e62811a3e2019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
= END
= START
R4edff70199ce6659c8739ee541adb772
aeb2ee83f309c966cbb9fb8c9d92e6f52019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
R4edff70199ce6659c8739ee541adb772
29942dc723b0c19cd47c078e62811a3e2019-02-08 22:19:07 +
2009-07-11 12:26:57 +01002009-07-11 11:59:00 +0100
b8780cf5f2ce52e0e880ae32bfac2f958d72c8ce9830cd1232ce606f3ea906fb
 RSPBn0/10/1001970-01-01 01:00:00
+0100
= END

Should those be there?

Colin

On Fri, 8 Feb 2019 at 22:02, Michael Hendry  wrote:
>
> > On 8 Feb 2019, at 17:26, John Ralls  wrote:
> >
> >
> >
> >> On Feb 8, 2019, at 8:28 AM, Colin Law  wrote:
> >>
> >> On Fri, 8 Feb 2019 at 15:31, Michael Hendry 
> >> wrote:> ...
> >>> | => ls -lt
> >>> total 84324
> >>> -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
> >>> MDH.gnucash.tmp-ea6yhc
> >>> -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
> >>> MDH.gnucash.20190208000345.log
> >>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 
> >>> MDH.gnucash.0.82823.LNK
> >>> -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
> >>> -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
> >>> MDH.gnucash.20190207202353.log
> >>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
> >>> -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
> >>> MDH.gnucash.20190207202200.log
> >>> -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
> >>> MDH.gnucash.20190208000443.gnucash
> >>> -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
> >>> MDH.gnucash.20190207185926.log
> >>> -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
> >>> MDH.gnucash.20190207202348.gnucash
> >>> -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
> >>> MDH.gnucash.20190207202153.gnucash
> >>>
> >>> There is no corresponding crash report, so I conclude that GC has failed 
> >>> to tidy up properly before closing.
> >>
> >> That looks odd.  Notice that the last successful save was 7 Feb 20:23.
> >> Then it appears that GC was started at 8 Feb 00:03, a log file of 95k
>
> Actually, the first file was modified on 8th Feb at 00:01, followed by the 
> lock file at 00:03.
>
> The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I 
> suspect that it’s part of the compression process that eventually results in 
> a new MDH.gnucash file.
>
> >> bytes was created (which seems large) but the results of that work
> >> were not saved.  I don't know, but it may be that the file
> >> MDH.gnucash.tmp-ea6yhc is the result of the first half of the save
> >> before it is compressed and the files renamed but I don't know.  How
> >> you could get a log file that large in one mi

Re: [GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

> On Feb 8, 2019, at 2:02 PM, Michael Hendry  wrote:
> 
>> On 8 Feb 2019, at 17:26, John Ralls  wrote:
>> 
>> 
>> 
>>> On Feb 8, 2019, at 8:28 AM, Colin Law  wrote:
>>> 
>>> On Fri, 8 Feb 2019 at 15:31, Michael Hendry 
>>> wrote:> ...
 | => ls -lt
 total 84324
 -rw-r--r--  1 michaelhendry  staff   221184  8 Feb 00:04 
 MDH.gnucash.tmp-ea6yhc
 -rw-r--r--  1 michaelhendry  staff95629  8 Feb 00:04 
 MDH.gnucash.20190208000345.log
 -rw---  2 michaelhendry  staff0  8 Feb 00:03 
 MDH.gnucash.0.82823.LNK
 -rw---  2 michaelhendry  staff0  8 Feb 00:03 MDH.gnucash.LCK
 -rw-r--r--  1 michaelhendry  staff  809  8 Feb 00:01 
 MDH.gnucash.20190207202353.log
 -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 MDH.gnucash
 -rw-r--r--  1 michaelhendry  staff  853  7 Feb 20:23 
 MDH.gnucash.20190207202200.log
 -rwx--  2 michaelhendry  staff  1136826  7 Feb 20:23 
 MDH.gnucash.20190208000443.gnucash
 -rw-r--r--  1 michaelhendry  staff23810  7 Feb 20:22 
 MDH.gnucash.20190207185926.log
 -rwx--  1 michaelhendry  staff  1136752  7 Feb 20:22 
 MDH.gnucash.20190207202348.gnucash
 -rwx--  1 michaelhendry  staff  1136766  7 Feb 18:59 
 MDH.gnucash.20190207202153.gnucash
 
 There is no corresponding crash report, so I conclude that GC has failed 
 to tidy up properly before closing.
>>> 
>>> That looks odd.  Notice that the last successful save was 7 Feb 20:23.
>>> Then it appears that GC was started at 8 Feb 00:03, a log file of 95k
> 
> Actually, the first file was modified on 8th Feb at 00:01, followed by the 
> lock file at 00:03.
> 
> The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I 
> suspect that it’s part of the compression process that eventually results in 
> a new MDH.gnucash file.
> 
>>> bytes was created (which seems large) but the results of that work
>>> were not saved.  I don't know, but it may be that the file
>>> MDH.gnucash.tmp-ea6yhc is the result of the first half of the save
>>> before it is compressed and the files renamed but I don't know.  How
>>> you could get a log file that large in one minute I don't know.  I see
>>> you have posted some of the contents and suggested they don't look
>>> right.
>> 
>> Scheduled transactions is how he could get 95K of log file in milliseconds. 
>> 
>> Good eye, noticing the temp file: The save failed for some reason and left 
>> GnuCash in a state where it quit without removing the lock. It's too bad 
>> that we overwrite trace files on MacOS. It would be useful to see if 
>> anything got logged about the save failing.
>> 
>> I think it's time to open a bug on this.
>> 
>> Regards,
>> John Ralls
> 
> Thanks, John.
> 
> Is it up to me to initiate this? 

It works best if you do, but if you prefer not to I'll do it for you with the 
information in this thread.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

> On Feb 8, 2019, at 2:02 PM, Michael Hendry  wrote:
> 
> Actually, the first file was modified on 8th Feb at 00:01, followed by the 
> lock file at 00:03.
> 
> The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I 
> suspect that it’s part of the compression process that eventually results in 
> a new MDH.gnucash file.
> 

That file that was touched at 00:01 is the previous session's log file as is 
indicated by the timestamp in the file name.

Try renaming the tmp file to something ending in gz and then run gunzip on it. 
Unless the gzip is borked it should turn into a text file.
After that diff it with MDH.gnucash to see what's been added or deleted.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 23:54, John Ralls  wrote:
> 
> 
> 
>> On Feb 8, 2019, at 2:02 PM, Michael Hendry  wrote:
>> 
>> Actually, the first file was modified on 8th Feb at 00:01, followed by the 
>> lock file at 00:03.
>> 
>> The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I 
>> suspect that it’s part of the compression process that eventually results in 
>> a new MDH.gnucash file.
>> 
> 
> That file that was touched at 00:01 is the previous session's log file as is 
> indicated by the timestamp in the file name.

OK, I missed that detail.

It raises a question to me (probably not relevant to this problem) - why would 
a log file have to be modified (or just touched) at the beginning of a new 
session?

> 
> Try renaming the tmp file to something ending in gz and then run gunzip on 
> it. Unless the gzip is borked it should turn into a text file.
> After that diff it with MDH.gnucash to see what's been added or deleted.

| ~/tmp/BUG @ Michaels-iMac (michaelhendry) 
| => gunzip temp.gz
gunzip: temp.gz: unexpected end of file
gunzip: temp.gz: uncompress failed

Running gunzip on MDH.gnucash (appropriately renamed) expands it into an xml 
file, as expected.

Michael

___
gnucash-user mailing list
gnucash-user@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.

Re: [GNC] postpone reconciliation broken: ignores my changes

[Michael Hendry]

> On 8 Feb 2019, at 23:48, John Ralls  wrote:
> 
>> 
>> Is it up to me to initiate this? 
> 
> It works best if you do, but if you prefer not to I'll do it for you with the 
> information in this thread.
> 
> Regards,
> John Ralls

I think you would express the problem more coherently than I. But I’m happy to 
do any further experiments necessary to elucidate this further.

Michael

___
gnucash-user mailing list
gnucash-user@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.

[GNC] Help Resolving AP Issue

[tbalaban]

Hi All,

When still getting my arms around how to properly post transactions I think
I did a fewdirect posts to Accounts Payable instead of processing a proper
payment using the payment processing tool. 

I see on my Balance Sheet a different number than I see in my Aged Accounts
Payable. The Balance Sheet AP is much larger.

My question is how can track down these incorrect transactions that were
posted AP but to a speciific vendor? I think I may have found one of them
but other than the fact I can't see the item on the vendor report, I can't
see a way to find the detail I'm looking for.

Any suggestions wil be greatly appreciated.



--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@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.