Re: [GNC] Intermittent Crash when using recent File dropdown list. Filed as bug # 799215

2024-01-11 Thread Tommy Trussell
On Wed, Jan 10, 2024 at 7:00 PM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:

> Also, since it is prompting you to save, that tells me something was
> edited without a save. Perhaps manually save, then attempt to switch. At
> least that should determine if the crash is happening on save, or upon
> opening the other book.
>

I too am trying to track down some crashes and unfortunately I am also
trying to get my bookkeeping done. I highlight this comment because maybe
it's somehow related. I'm running 5.4.1 Flatpak on Ubuntu 22.04.3

My main GnuCash data file (with many years of transactions and about 90
scheduled transactions) ALWAYS shows that it needs to save when I first
open it. I suspect it could be a scheduled transaction, maybe a "zombie"
one that's no longer used, but I haven't taken the time to track it down...

I will note that as soon as I open the data file, the logfile is already
created with essentially nothing in it.

Here's an example from today where I opened the data file, looked for
something and then closed it without saving. Pretty much always it starts
with four START / END sequences at the top.


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
-
= START
= END
= START
= END
= START
= END
= START
= END
= START
D e711a885231d43c6b976d4d1e38b2c58 57776cb2c4ab4a498853932a0d7ec834
2024-01-11 19:20:49 2024-01-11 19:20:49 2024-01-11 10:59:00 n 0/1 0/100
1970-01-01 00:00:00
= END
= START
D 300783928b674543aeeb5950d8b03571 dacb85ebf8f84736a31adede7ad81967
2024-01-11 19:20:53 2024-01-11 19:20:53 2024-01-11 10:59:00 n 0/1 0/100
1970-01-01 00:00:00
= END
= START
D 1d97105a3b1a456d9ffe399965717d7d ae655ba0353f4b6a915b2dec1c67b6b0
2024-01-11 19:20:53 2024-01-11 19:20:53 2024-01-11 10:59:00 n 0/1 0/100
1970-01-01 00:00:00
= END
= START
D 2a91e27362804a5f87185ccd4c9c7f49 095fdbe44e8340b6bb31a91cf1f814d2
2024-01-11 19:20:53 2024-01-11 19:20:53 2024-01-11 10:59:00 n 0/1 0/100
1970-01-01 00:00:00
= END



> -
> 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
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


Re: [GNC] Intermittent Crash when using recent File dropdown list. Filed as bug # 799215

2024-01-10 Thread Stephen M. Butler

On 1/10/24 16:59, Adrien Monteleone wrote:
Have you tried opening the (other) desired book directly via command 
line?


It may be the book you are attempting to switch to has an issue, and 
not saving the current one.


It works the second time I try.  So, not the book.  And yes, I've opened 
it multiple times after each crash.  It isn't the same book each time 
either.
Also, since it is prompting you to save, that tells me something was 
edited without a save. Perhaps manually save, then attempt to switch. 
At least that should determine if the crash is happening on save, or 
upon opening the other book.


Oh, I definitely did work.  The fact that when I restart GnC it doesn't 
complain about a lock file on the "old" book tells me that the save 
worked.  The lock file was on the "new" book.


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
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.


Re: [GNC] Intermittent Crash when using recent File dropdown list. Filed as bug # 799215

2024-01-10 Thread Adrien Monteleone

Have you tried opening the (other) desired book directly via command line?

It may be the book you are attempting to switch to has an issue, and not 
saving the current one.


Also, since it is prompting you to save, that tells me something was 
edited without a save. Perhaps manually save, then attempt to switch. At 
least that should determine if the crash is happening on save, or upon 
opening the other book.


Regards,
Adrien

On 1/10/24 6:05 PM, Stephen M. Butler wrote:

Ubuntu 23.10
GnC Build ID: git 5.4-117-gabb4a01ac8+(2023-12-01)

Intermittent when changing books using the recent file dropdown list.

I pick the book I want next from the File recent dropdown list.
GnC asks if I want to save the existing opened book.  I say yes.
Soon thereafter the program goes away.  No stacktrace that I can find.

Start GnC again and it opens the book I was in.  Again I pick from the 
recent file dropdown.  I don't think it asks if I want to save. But I do 
get the Lock File dialogue.  I tell it to open anyway.  It opens.


This happens infrequent and I can't predict when it will happen.

Apparently happens after the lock file is created for the new book but 
before it is read into memory.


What steps do I need to take to get additional information the next time 
this (apparently random) happens?




___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
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.


[GNC] Intermittent Crash when using recent File dropdown list. Filed as bug # 799215

2024-01-10 Thread Stephen M. Butler

Ubuntu 23.10
GnC Build ID: git 5.4-117-gabb4a01ac8+(2023-12-01)

Intermittent when changing books using the recent file dropdown list.

I pick the book I want next from the File recent dropdown list.
GnC asks if I want to save the existing opened book.  I say yes.
Soon thereafter the program goes away.  No stacktrace that I can find.

Start GnC again and it opens the book I was in.  Again I pick from the 
recent file dropdown.  I don't think it asks if I want to save. But I do 
get the Lock File dialogue.  I tell it to open anyway.  It opens.


This happens infrequent and I can't predict when it will happen.

Apparently happens after the lock file is created for the new book but 
before it is read into memory.


What steps do I need to take to get additional information the next time 
this (apparently random) happens?


--
Stephen M Butler
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
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.