Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
Hello, It's been quite a while since I have chimed in here. At the risk of going off-topic for a moment, I'd like to start by expressing my gratitude to the entire team that develops and maintains GnuCash. I switched from Quicken on 1/1/2020 and have never looked back. I started with GnuCash 2.8, then a few months ago I upgraded to a more recent release. The feature that got added to allow me to type any part of an account name when entering splits has been a game-changer for me and has made me so much more efficient. So consider this a belated thank you just for that! Back to the topic at hand, I actually have been running MySQL as the data store for the past two years. I agree wholeheartedly that it's not for the user who is not well seasoned with the setup and care of an RDMS. I have twice had to deal with the server instance randomly not wanting to start and ended up having to reinstall the server. On the other hand, I also do a lot of my own custom reporting and analytics from MS Access, and the performance that the MySQL back-end is providing me is pretty impressive. I too have danced with the devil (a.k.a. "voided the warranty") by doing selective data updates. I am mostly on Windows and as far as I can tell the Python bindings were not an option for me like they might be on Linux? Regardless, I tend to mostly update transaction descriptions (or notes or memos, I always get the 3 confused) values to implement my homegrown naming rules. On occasion, I'll manually clean up funky data -- such as a bunch of splits that have no $ value. I only do these updates when the GnuCash app is closed. I learned pretty quickly to stay away from anything that the GnuCash application is actually managing in memory such as the budget data. I work on back-end database systems for a living and am used to having to figure out the *rules* and logic that I may wish were in the DB layer but are not. The ability to get any the raw data store when and how I want is one thing that makes GnuCash so appealing to me vs a product like Quickbooks which basically abstracts everything (and can be painfully slow to boot). One thing that I have never been able to figure out is if I leave the regular GnuCash application running for a few hours when I return to my PC and try to do anything it will tell me "Unable to Save to Database" and I then must exit GnuCash and restart it to clear that error. Thank You once again for everything! On Fri, Jan 21, 2022 at 11:44 AM john wrote: > Very few users will be able to manage a MySQL database server safely. > Fortunately GnuCash provides a SQLite3 backend that doesn't require any > database admin skills. The only caveat is that unlike XML it doesn't write > a fresh file every session so you need to arrange backups on your own; the > OS's built-in snapshotting facility (rather grandly named Time Machine on > macOS and simply Windows Backup on Windows) is good for this, just make > sure that your GnuCash data folder is included in its list of things to > back up. > > Regards, > John Ralls > > > > On Jan 21, 2022, at 6:45 AM, Thomas Forrester > wrote: > > > > Seems like a lot of work. No doubt you're finding interesting anomalies, > > but... > > > > Rather than using xml data files, which have always seemed odd to me (a > la, > > this thread), if you use a MySQL database instead, all saves are > automatic > > and completely bypass the need for all this testing. You still have to > > save each transaction, or edits to a transaction (Enter key), but > otherwise > > you can freely close the program without any worries about loosing data, > > and there is no save prompt on the way out. I've run with a MySQL > database > > from the start without any problems at all. Just a thought, and I > > recognize some may have reasons not to choose that path, although I'm not > > sure what they would be. > > > > On Thu, Jan 20, 2022, 11:22 PM Peter wrote: > > > >> John, > >> Well yes it did terminate or close. > >> gnucash was closed and was then reopened without any reported issue. > >> Other than it failed to save the changes and delete the lock file. > >> Maybe if you could tell me how to confirm it closed or terminated > >> correctly, I will go and test and see what happens. > >> This issue I noted in Test#2 was actually caused by me not following > my > >> own test process. > >> > >> On 21/01/2022 04:48, John Layman wrote: > >> > >> The test cases that appear to have failed aren't conclusive, however, > >> without co > >> nfirming that GnuCash had actually terminated, and terminated normally. > >> > >> -
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
>>> Rather than using xml data files, which have always seemed odd to me <<< There are pros and cons to substituting a RDBMS for XML. Since GnuCash was originally designed for an in-memory data store, the XML is it's native persistence system. Over time, it has been altered to substitute a SQL database as the store, but not with a clean relational data model. I have been using GnuCash for both business and personal accounting since 01-Jan-2010, Plus, I imported prior data for long-term investments, etc. So my files are rather large. I've experimented with using SQLite, but not found it advantageous. While it is quicker on the backend (ie. When you quit the program) it is noticeably slower on the frontend. Because it is designed for an in-memory store, it has to load the entire database into memory up front, and that takes more time reading the data from SQLite than simply sucking it in from a flat file. I'm sure that is true with any RDBMS. Another con to using a RDBMS so far as I am concerned is the loss of 'revert' capability. There are occasional situations where it is convenient to simply scrub a session and start over. That's a great deal more complicated restoring a relational database from backup. When I first started using GnuCash, I expected increasing file size to be a problem. I had formerly used Microsoft Money, which had an excellent ability to discard older data without the loss of stuff that needed to be retained long-term. But twelve years on, I've not found that to be a problem. The folks maintaining this software have done a great job of keeping the reading/writing of the XML data store efficient. ___ 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] Exiting gnucash Lock file Vol 226, Issue 57
The presence of the lock file and an unchanged XML data store would be the expected condition if GnuCash had yet to terminate for some reason. A simple way in Windows to check for termination would be to run the test with a task manager open. GnuCash would blink out once it terminated, at which point the presence of the lock file would conclusively indicate a failure of some sort. But it would also be necessary to establish that GnuCash did not terminate abnormally for some reason. Only then would the presence of the lock file, etc. be a clear indication of a defect in GnuCash itself. -Original Message- From: gnucash-user On Behalf Of Peter Sent: Friday, January 21, 2022 12:22 AM To: john.lay...@laymanandlayman.com; gnucash-user@gnucash.org Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 John, Well yes it did terminate or close. gnucash was closed and was then reopened without any reported issue. Other than it failed to save the changes and delete the lock file. Maybe if you could tell me how to confirm it closed or terminated correctly, I will go and test and see what happens. This issue I noted in Test#2 was actually caused by me not following my own test process. On 21/01/2022 04:48, John Layman wrote: The test cases that appear to have failed aren't conclusive, however, without co nfirming that GnuCash had actually terminated, and terminated normally. -Original Message- From: gnucash-user [1] On Behalf Of Peter Sent: Thursday, January 20, 2022 9:39 AM To: [2]gnucash-user@gnucash.org Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 Here is the testing methods I used to verify the issue I have noted. Selected a known small good gnucash data file. Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB GNUCAS H Storage type : XML and compressed Operating system: Windows 10 GNUCASH versio n 4.9 The opening method in ALL test was to use the GNUCASH icon on the TASKBAR and then select the recent (test) file If the LOCK file was not deleted it was r emoved using the windows File Explorer - Test #1: - change, Save Button and then File->Quit Result: This was repeated 5 times each time the same result - Lock file was dele ted and the change was Saved. - Test #2 - change then File>Quit and save at 15 seconds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file This test was actual performed more than 5 times but I did note 5 of 5 in one contiguous run. There were a few test that asked to save the transa ction prior to the question of save the file I was never able to get it to repea t twice in a row. - Test #3 - change and exit File->Quit wait for the Save dialogue then let it time out Result: In test 5 of 5 Lock file was deleted and the change was saved in the dat a file - Test #4 - change and wait for autosave then File->Quit Result: In test 5 of 5 Lock file was deleted and the change was saved in the dat a file - Test #5 - change and wait for autosave then use X method Result: In test 5 of 5 Lock file was deleted and the change was saved in the dat a file - Test #6 - change then use X method wait for the save dialogue and save at 15 sec onds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file - Conclusion: There is an issue in exiting with the SAVE button enabled/Highlighted and comply ing with the dialogue to SAVE the Data file. Test#2 and Test#6 Four methods of exiting that do delete the LOCK file and SAVE the latest changes A:Waiting to exit after an Autosave then File->Quit B:forcing a Save by using the SAVE button then File->Quit C:Waiting to exit after an Autosave then the X method D:forcing a Save by using the SAVE button then the X method X method works if you do a SAVE using the Save Button or wait till after an Au tosave then exit via the X method There is an issue with exiting and relying on gnucash to save the data if gnucas h produces the dialogue to SAVE the data then File->Quit or the X method The Sav e does not work and the LOCK file is not deleted. I cannot safely say I do not use the X method as I now have doub
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
Good point, John. I agree that MySQL has a large administrative footprint and certainly does take an IT mindset. I hadn't considered, or even realized that GnuCash could use a SQLite database. Maybe that's because the use of SQL as a backend was just a beta thing back when I boarded this bus? IDK. Maybe it was because I already was using MySQL in running a couple of Internet radio stations. So thanks for your thoughts on this. I'm actually now reading up on how to switch to SQLite for my own data as I do think MySQL is a bit of overkill. Apparently as simple as just opening the existing MySQL database, then saving as SQLite, so that's easy enough. But I'll also need to consider ODBC connectivity to Microsoft Access, too, because I sometimes "look" at the data and make some adjustments where needed like if a reconciliation gets messed up because I did something stupid. One day, I hope to look into some alternative reporting solutions using MS Access' report features, so I'd need to keep that connection in place if I'm going to make the switch. On Fri, Jan 21, 2022 at 10:43 AM john wrote: > Very few users will be able to manage a MySQL database server safely. > Fortunately GnuCash provides a SQLite3 backend that doesn't require any > database admin skills. The only caveat is that unlike XML it doesn't write > a fresh file every session so you need to arrange backups on your own; the > OS's built-in snapshotting facility (rather grandly named Time Machine on > macOS and simply Windows Backup on Windows) is good for this, just make > sure that your GnuCash data folder is included in its list of things to > back up. > > Regards, > John Ralls > > > > On Jan 21, 2022, at 6:45 AM, Thomas Forrester > wrote: > > > > Seems like a lot of work. No doubt you're finding interesting anomalies, > > but... > > > > Rather than using xml data files, which have always seemed odd to me (a > la, > > this thread), if you use a MySQL database instead, all saves are > automatic > > and completely bypass the need for all this testing. You still have to > > save each transaction, or edits to a transaction (Enter key), but > otherwise > > you can freely close the program without any worries about loosing data, > > and there is no save prompt on the way out. I've run with a MySQL > database > > from the start without any problems at all. Just a thought, and I > > recognize some may have reasons not to choose that path, although I'm not > > sure what they would be. > > > > On Thu, Jan 20, 2022, 11:22 PM Peter wrote: > > > >> John, > >> Well yes it did terminate or close. > >> gnucash was closed and was then reopened without any reported issue. > >> Other than it failed to save the changes and delete the lock file. > >> Maybe if you could tell me how to confirm it closed or terminated > >> correctly, I will go and test and see what happens. > >> This issue I noted in Test#2 was actually caused by me not following > my > >> own test process. > >> > >> On 21/01/2022 04:48, John Layman wrote: > >> > >> The test cases that appear to have failed aren't conclusive, however, > >> without co > >> nfirming that GnuCash had actually terminated, and terminated normally. > >> > >> -Original Message- > >> From: gnucash-user [1] >> ieee@gnucash.org> On > >> Behalf Of Peter > >> Sent: Thursday, January 20, 2022 9:39 AM > >> To: [2]gnucash-user@gnucash.org > >> Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 > >> > >> Here is the testing methods I used to verify the issue I have noted. > >> > >> Selected a known small good gnucash data file. > >> Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate > 2TB > >> GNUCAS > >> H Storage type : XML and compressed Operating system: Windows 10 > GNUCASH > >> versio > >> n 4.9 The opening method in ALL test was to use the GNUCASH icon on the > >> TASKBAR > >> and then select the recent (test) file If the LOCK file was not deleted > it > >> was r > >> emoved using the windows File Explorer > >> > >> > >> > >> > > >> - > >> > >> Test #1: - change, Save Button and then File->Quit > >> > >> Result: This was repeated 5 times each time the same re
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
Very few users will be able to manage a MySQL database server safely. Fortunately GnuCash provides a SQLite3 backend that doesn't require any database admin skills. The only caveat is that unlike XML it doesn't write a fresh file every session so you need to arrange backups on your own; the OS's built-in snapshotting facility (rather grandly named Time Machine on macOS and simply Windows Backup on Windows) is good for this, just make sure that your GnuCash data folder is included in its list of things to back up. Regards, John Ralls > On Jan 21, 2022, at 6:45 AM, Thomas Forrester wrote: > > Seems like a lot of work. No doubt you're finding interesting anomalies, > but... > > Rather than using xml data files, which have always seemed odd to me (a la, > this thread), if you use a MySQL database instead, all saves are automatic > and completely bypass the need for all this testing. You still have to > save each transaction, or edits to a transaction (Enter key), but otherwise > you can freely close the program without any worries about loosing data, > and there is no save prompt on the way out. I've run with a MySQL database > from the start without any problems at all. Just a thought, and I > recognize some may have reasons not to choose that path, although I'm not > sure what they would be. > > On Thu, Jan 20, 2022, 11:22 PM Peter wrote: > >> John, >> Well yes it did terminate or close. >> gnucash was closed and was then reopened without any reported issue. >> Other than it failed to save the changes and delete the lock file. >> Maybe if you could tell me how to confirm it closed or terminated >> correctly, I will go and test and see what happens. >> This issue I noted in Test#2 was actually caused by me not following my >> own test process. >> >> On 21/01/2022 04:48, John Layman wrote: >> >> The test cases that appear to have failed aren't conclusive, however, >> without co >> nfirming that GnuCash had actually terminated, and terminated normally. >> >> -Original Message----- >> From: gnucash-user [1]> ieee@gnucash.org> On >> Behalf Of Peter >> Sent: Thursday, January 20, 2022 9:39 AM >> To: [2]gnucash-user@gnucash.org >> Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 >> >> Here is the testing methods I used to verify the issue I have noted. >> >> Selected a known small good gnucash data file. >> Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB >> GNUCAS >> H Storage type : XML and compressed Operating system: Windows 10 GNUCASH >> versio >> n 4.9 The opening method in ALL test was to use the GNUCASH icon on the >> TASKBAR >> and then select the recent (test) file If the LOCK file was not deleted it >> was r >> emoved using the windows File Explorer >> >> >> >> >> - >> >> Test #1: - change, Save Button and then File->Quit >> >> Result: This was repeated 5 times each time the same result - Lock file >> was dele >> ted and the change was Saved. >> >> >> >> - >> >> Test #2 - change then File>Quit and save at 15 seconds on timer >> >> Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT >> saved in >> the data file This test was actual performed more than 5 times but I did >> note 5 >> of 5 in one contiguous run. There were a few test that asked to save the >> transa >> ction prior to the question of save the file I was never able to get it to >> repea >> t twice in a row. >> >> >> >> - >> >> Test #3 - change and exit File->Quit wait for the Save dialogue then let >> it time >> out >> >> Result: In test 5 of 5 Lock file was deleted and the change was saved in >> the dat >> a file >> >> >> >> - >> >> Test #4 - change and wait for autosave then File->Quit >> >> Result: In test 5 of 5 Lock file was deleted and the change was saved in >> the dat >> a file >> >> >> >> - >&g
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
Seems like a lot of work. No doubt you're finding interesting anomalies, but... Rather than using xml data files, which have always seemed odd to me (a la, this thread), if you use a MySQL database instead, all saves are automatic and completely bypass the need for all this testing. You still have to save each transaction, or edits to a transaction (Enter key), but otherwise you can freely close the program without any worries about loosing data, and there is no save prompt on the way out. I've run with a MySQL database from the start without any problems at all. Just a thought, and I recognize some may have reasons not to choose that path, although I'm not sure what they would be. On Thu, Jan 20, 2022, 11:22 PM Peter wrote: >John, >Well yes it did terminate or close. >gnucash was closed and was then reopened without any reported issue. >Other than it failed to save the changes and delete the lock file. >Maybe if you could tell me how to confirm it closed or terminated >correctly, I will go and test and see what happens. >This issue I noted in Test#2 was actually caused by me not following my >own test process. > >On 21/01/2022 04:48, John Layman wrote: > > The test cases that appear to have failed aren't conclusive, however, > without co > nfirming that GnuCash had actually terminated, and terminated normally. > > -Original Message- > From: gnucash-user [1] ieee@gnucash.org> On > Behalf Of Peter > Sent: Thursday, January 20, 2022 9:39 AM > To: [2]gnucash-user@gnucash.org > Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 > > Here is the testing methods I used to verify the issue I have noted. > > Selected a known small good gnucash data file. > Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB > GNUCAS > H Storage type : XML and compressed Operating system: Windows 10 GNUCASH > versio > n 4.9 The opening method in ALL test was to use the GNUCASH icon on the > TASKBAR > and then select the recent (test) file If the LOCK file was not deleted it > was r > emoved using the windows File Explorer > > > > > - > > Test #1: - change, Save Button and then File->Quit > > Result: This was repeated 5 times each time the same result - Lock file > was dele > ted and the change was Saved. > > > > - > > Test #2 - change then File>Quit and save at 15 seconds on timer > > Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT > saved in > the data file This test was actual performed more than 5 times but I did > note 5 > of 5 in one contiguous run. There were a few test that asked to save the > transa > ction prior to the question of save the file I was never able to get it to > repea > t twice in a row. > > > > - > > Test #3 - change and exit File->Quit wait for the Save dialogue then let > it time > out > > Result: In test 5 of 5 Lock file was deleted and the change was saved in > the dat > a file > > > > - > > Test #4 - change and wait for autosave then File->Quit > > Result: In test 5 of 5 Lock file was deleted and the change was saved in > the dat > a file > > > > - > > Test #5 - change and wait for autosave then use X method > > Result: In test 5 of 5 Lock file was deleted and the change was saved in > the dat > a file > > > > - > > Test #6 - change then use X method wait for the save dialogue and save at > 15 sec > onds on timer > > Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT > saved in > the data file > > > > - > > Conclusion: > > There is an issue in exiting with the SAVE button enabled/Highlighted and > comply > ing with the dialogue to SAVE the Data file. > Test#2 and Test#6 > > Four methods of exiting that do delete the LOCK file and SAVE the latest > changes > A:Waiting to exit after an Autosave then File->Quit > B:forcing a Save by using the SAVE button then File->Qui
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
The test cases that appear to have failed aren't conclusive, however, without confirming that GnuCash had actually terminated, and terminated normally. -Original Message- From: gnucash-user On Behalf Of Peter Sent: Thursday, January 20, 2022 9:39 AM To: gnucash-user@gnucash.org Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 Here is the testing methods I used to verify the issue I have noted. Selected a known small good gnucash data file. Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB GNUCASH Storage type : XML and compressed Operating system: Windows 10 GNUCASH version 4.9 The opening method in ALL test was to use the GNUCASH icon on the TASKBAR and then select the recent (test) file If the LOCK file was not deleted it was removed using the windows File Explorer - Test #1: - change, Save Button and then File->Quit Result: This was repeated 5 times each time the same result - Lock file was deleted and the change was Saved. - Test #2 - change then File>Quit and save at 15 seconds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file This test was actual performed more than 5 times but I did note 5 of 5 in one contiguous run. There were a few test that asked to save the transaction prior to the question of save the file I was never able to get it to repeat twice in a row. - Test #3 - change and exit File->Quit wait for the Save dialogue then let it time out Result: In test 5 of 5 Lock file was deleted and the change was saved in the data file - Test #4 - change and wait for autosave then File->Quit Result: In test 5 of 5 Lock file was deleted and the change was saved in the data file - Test #5 - change and wait for autosave then use X method Result: In test 5 of 5 Lock file was deleted and the change was saved in the data file - Test #6 - change then use X method wait for the save dialogue and save at 15 seconds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file - Conclusion: There is an issue in exiting with the SAVE button enabled/Highlighted and complying with the dialogue to SAVE the Data file. Test#2 and Test#6 Four methods of exiting that do delete the LOCK file and SAVE the latest changes A:Waiting to exit after an Autosave then File->Quit B:forcing a Save by using the SAVE button then File->Quit C:Waiting to exit after an Autosave then the X method D:forcing a Save by using the SAVE button then the X method X method works if you do a SAVE using the Save Button or wait till after an Autosave then exit via the X method There is an issue with exiting and relying on gnucash to save the data if gnucash produces the dialogue to SAVE the data then File->Quit or the X method The Save does not work and the LOCK file is not deleted. I cannot safely say I do not use the X method as I now have doubts about it, I may use it or I may not. Hope this helps someone as now I understand why sometimes it does work and does NOT work, there is a bug in it or is it a misinterpreted enhancement. ___ 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] Exiting gnucash Lock file Vol 226, Issue 57
I am not sure that I am actually replying to the last email in this thread. Gmail seems to shuffle messages and duplicate them until it is impossible to figure out the order unless you go back and look at the timestamps in all the headers, far too much work. I am trying to reply to the messages about how to ascertain when GnuCash has actually finished saving all the edits and closed completely, including deleting the lock file. In my experience, when I am ready to close the file after my last edit, I first look in the OS window header to see if there is an asterisk in front of the filename. If there is, then I need to use File > Save or use the equivalent mouse action to get rid of the asterisk. Then I move the highlight around the window until I see that buttons turn bright when moused over. While GnuCash is 'thinking' or unable to respond to user input for some reason the curser highlight does not work. Then I use File > Quit, or Ctrl-Q or the X button in the OS header to close GnuCash. At that stage, if there are any remaining pending edits that I forgot to save, there is a pop-up pointing to one of those pending edits, so I resolve them and repeat the File > Save, tho they should have been resolved in the previous steps. Last, I do not consider GnuCash to be closed until it has disappeared completely from the workspace. That normally takes several seconds after clicking File > Quit. I have a very large data file that takes gigabytes of RAM when open, and sometimes I work on it from a remote location or have other factors in play so it can sometimes take several minutes to complete a successful file save, tho it usually takes just a few seconds. That is why I wait for the mouse highlight to trigger the expected button color changes or mouse over comments in addition to the missing asterisk. When I follow that procedure, I only find the lock file to remain if GnuCash has actually crashed.. I normally run GnuCash in a Linux environment, but in my memory of when I used to run it in Windows, the behavior was similar, but slower. On Thu, Jan 20, 2022 at 8:39 AM Peter wrote: > Here is the testing methods I used to verify the issue I have noted. > > Selected a known small good gnucash data file. > Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB > GNUCASH Storage type : XML and compressed > Operating system: Windows 10 > GNUCASH version 4.9 > The opening method in ALL test was to use the GNUCASH icon on the > TASKBAR and then select the recent (test) file > If the LOCK file was not deleted it was removed using the windows File > Explorer > > > > - > > Test #1: - change, Save Button and then File->Quit > > Result: This was repeated 5 times each time the same result - Lock file > was deleted and the change was Saved. > > > - > > Test #2 - change then File>Quit and save at 15 seconds on timer > > Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT > saved in the data file > This test was actual performed more than 5 times but I did note 5 of 5 > in one contiguous run. There were a few test that asked to save the > transaction prior to the question of save the file > I was never able to get it to repeat twice in a row. > > > - > > Test #3 - change and exit File->Quit wait for the Save dialogue then let > it time out > > Result: In test 5 of 5 Lock file was deleted and the change was saved in > the data file > > > - > > Test #4 - change and wait for autosave then File->Quit > > Result: In test 5 of 5 Lock file was deleted and the change was saved in > the data file > > > - > > Test #5 - change and wait for autosave then use X method > > Result: In test 5 of 5 Lock file was deleted and the change was saved in > the data file > > > - > > Test #6 - change then use X method wait for the save dialogue and save > at 15 seconds on timer > > Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT > saved in the data file > > > - > > Conclusion: > > There is an issue in exiting with the SAVE button enabled/Highlighted > and complying with the dialogue to SAVE the Data file. > Test#2 and Test#6 > > Four methods of exiting that do delete the LOCK file and SAVE the latest > changes > A:Waiting to exit after an Autosave then File->Quit > B:forcing a Save by
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
John, Well yes it did terminate or close. gnucash was closed and was then reopened without any reported issue. Other than it failed to save the changes and delete the lock file. Maybe if you could tell me how to confirm it closed or terminated correctly, I will go and test and see what happens. This issue I noted in Test#2 was actually caused by me not following my own test process. On 21/01/2022 04:48, John Layman wrote: The test cases that appear to have failed aren't conclusive, however, without co nfirming that GnuCash had actually terminated, and terminated normally. -Original Message- From: gnucash-user [1] On Behalf Of Peter Sent: Thursday, January 20, 2022 9:39 AM To: [2]gnucash-user@gnucash.org Subject: Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57 Here is the testing methods I used to verify the issue I have noted. Selected a known small good gnucash data file. Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB GNUCAS H Storage type : XML and compressed Operating system: Windows 10 GNUCASH versio n 4.9 The opening method in ALL test was to use the GNUCASH icon on the TASKBAR and then select the recent (test) file If the LOCK file was not deleted it was r emoved using the windows File Explorer - Test #1: - change, Save Button and then File->Quit Result: This was repeated 5 times each time the same result - Lock file was dele ted and the change was Saved. - Test #2 - change then File>Quit and save at 15 seconds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file This test was actual performed more than 5 times but I did note 5 of 5 in one contiguous run. There were a few test that asked to save the transa ction prior to the question of save the file I was never able to get it to repea t twice in a row. - Test #3 - change and exit File->Quit wait for the Save dialogue then let it time out Result: In test 5 of 5 Lock file was deleted and the change was saved in the dat a file - Test #4 - change and wait for autosave then File->Quit Result: In test 5 of 5 Lock file was deleted and the change was saved in the dat a file - Test #5 - change and wait for autosave then use X method Result: In test 5 of 5 Lock file was deleted and the change was saved in the dat a file - Test #6 - change then use X method wait for the save dialogue and save at 15 sec onds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file - Conclusion: There is an issue in exiting with the SAVE button enabled/Highlighted and comply ing with the dialogue to SAVE the Data file. Test#2 and Test#6 Four methods of exiting that do delete the LOCK file and SAVE the latest changes A:Waiting to exit after an Autosave then File->Quit B:forcing a Save by using the SAVE button then File->Quit C:Waiting to exit after an Autosave then the X method D:forcing a Save by using the SAVE button then the X method X method works if you do a SAVE using the Save Button or wait till after an Au tosave then exit via the X method There is an issue with exiting and relying on gnucash to save the data if gnucas h produces the dialogue to SAVE the data then File->Quit or the X method The Sav e does not work and the LOCK file is not deleted. I cannot safely say I do not use the X method as I now have doubts about it, I may use it or I may not. Hope this helps someone as now I understand why sometimes it does work and does NOT work, there is a bug in it or is it a misinterpreted enhancement. ___ gnucash-user mailing list [3]gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: [4]https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see [5]https://wiki.gnucash.org/wiki/Ma iling_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. References 1. mailto:gnucash-user-bounces+john.layman=ieee@gnucash.org 2. mailto:gnucash-user@gnucash.org 3. mailto:gnucash-user@gnucash.org 4. https://lists.gnucash.org/mai
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
Here is the testing methods I used to verify the issue I have noted. Selected a known small good gnucash data file. Storage Location: Local D: c: drive is Samsung SSD and D: is Seagate 2TB GNUCASH Storage type : XML and compressed Operating system: Windows 10 GNUCASH version 4.9 The opening method in ALL test was to use the GNUCASH icon on the TASKBAR and then select the recent (test) file If the LOCK file was not deleted it was removed using the windows File Explorer - Test #1: - change, Save Button and then File->Quit Result: This was repeated 5 times each time the same result - Lock file was deleted and the change was Saved. - Test #2 - change then File>Quit and save at 15 seconds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file This test was actual performed more than 5 times but I did note 5 of 5 in one contiguous run. There were a few test that asked to save the transaction prior to the question of save the file I was never able to get it to repeat twice in a row. - Test #3 - change and exit File->Quit wait for the Save dialogue then let it time out Result: In test 5 of 5 Lock file was deleted and the change was saved in the data file - Test #4 - change and wait for autosave then File->Quit Result: In test 5 of 5 Lock file was deleted and the change was saved in the data file - Test #5 - change and wait for autosave then use X method Result: In test 5 of 5 Lock file was deleted and the change was saved in the data file - Test #6 - change then use X method wait for the save dialogue and save at 15 seconds on timer Result: In test 5 of 5 Lock file was NOT deleted and the change was NOT saved in the data file - Conclusion: There is an issue in exiting with the SAVE button enabled/Highlighted and complying with the dialogue to SAVE the Data file. Test#2 and Test#6 Four methods of exiting that do delete the LOCK file and SAVE the latest changes A: Waiting to exit after an Autosave then File->Quit B: forcing a Save by using the SAVE button then File->Quit C: Waiting to exit after an Autosave then the X method D: forcing a Save by using the SAVE button then the X method X method works if you do a SAVE using the Save Button or wait till after an Autosave then exit via the X method There is an issue with exiting and relying on gnucash to save the data if gnucash produces the dialogue to SAVE the data then File->Quit or the X method The Save does not work and the LOCK file is not deleted. I cannot safely say I do not use the X method as I now have doubts about it, I may use it or I may not. Hope this helps someone as now I understand why sometimes it does work and does NOT work, there is a bug in it or is it a misinterpreted enhancement. ___ 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] Exiting gnucash Lock file Vol 226, Issue 57
Oh dear, In the excitement of finding out that someone else possibly had the problem I forgot to add. >> Your message has gotten detached from the thread.. NFI >> Do you save your data file on a hard drive? Do you encrypt it? Storage: Local disk separate from the OS drive. Has separate directory d:public\data\... Storage method:XML and compressed >> Do you use Windows or another OS? OS:Windows 10 and kept up to date as per MS demands Version of gnucash: 4.6, 4.7, 4.8 and 4.9 all exhibit the problem. >> Do you use cloud storage for backup? NO defiantly NO >> Can you think of any other commonality when the lock file is not deleted? Whats common? - Started after a SQLite test gnu version 4.6 . SQL directory was set to be different to the XML directory. - since gnucash 4.9 that SQL directory has been deleted but issue still remains I follow the standard process of installing the newest version directly on top of the previous version. (Seems to be the standard process.) I have tried to uninstall the previous version but no different. I suspect that there is something that I cannot find or that are hidden that I cannot remove as I don't know where. It would be nice if the uninstall process did give the option of delete anything that was hidden from normal beings view. i.e do a clean install. On 19/01/2022 14:32, David Carlson wrote: Peter, Your message has gotten detached from the thread.. We need more information to hazard a guess whether your issue is the same as that of Gyle or if it is just similar. Do you save your data file on a hard drive? Do you encrypt it? Do you use cloud storage for backup? Do you use Windows or another OS? Can you think of any other commonality when the lock file is not deleted? On Tue, Jan 18, 2022, 11:05 PM Peter <[1]pan...@iinet.net.au> wrote: This is interesting. I have had this problem of gnucash intermittently not removing the LOCK file for some time. My method of closing gnucash is firstly to save the data and the close using the menu. I always follow this process and never use the 'X' method. August 24, 2021 gnucash ver 4.6, I investigated using SQLlite instead of the compressed XML for data storage. SQLite worked but the resultant file(s) were much larger than the XML compressed version so I decided to continue to use the compressed XML. From that date (August 24, 2021) to today I still get gnucash intermittently not removing the LOCK file. This includes ver4.7, ver4.8 and ver4.9. It may happen ver4.6 but unsure. Ever time I updated I hoped it would resolve the issue but it still happens. About 20 days ago I deleted the SQL subdirectory and files from my local data disk. This seemed to make no difference to the issue. On 19/01/2022 06:17, [2]gnucash-user-requ...@gnucash.org wrote: > Send gnucash-user mailing list submissions to > [3]gnucash-user@gnucash.org > > To subscribe or unsubscribe via the World Wide Web, visit > [4]https://lists.gnucash.org/mailman/listinfo/gnucash-user > or, via email, send a message with subject or body 'help' to > [5]gnucash-user-requ...@gnucash.org > > You can reach the person managing the list at > [6]gnucash-user-ow...@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: Exiting GNUCash (D.) > 2. Re: Exiting GNUCash (David Carlson) > 3. OneDrive ([7]men...@fastmail.fm) > 4. Re: gnucash-user Digest, Vol 226, Issue 48 (Heide Wang) > 5. Re: OneDrive and GnuCash ([8]davidcousen...@gmail.com) > > ___ > > gnucash-user mailing list > [9]gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > [10]https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see [11]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 [12]gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: [13]https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see [14]https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies.
Re: [GNC] Exiting gnucash Lock file Vol 226, Issue 57
Peter, Your message has gotten detached from the thread.. We need more information to hazard a guess whether your issue is the same as that of Gyle or if it is just similar. Do you save your data file on a hard drive? Do you encrypt it? Do you use cloud storage for backup? Do you use Windows or another OS? Can you think of any other commonality when the lock file is not deleted? On Tue, Jan 18, 2022, 11:05 PM Peter wrote: > This is interesting. > > I have had this problem of gnucash intermittently not removing the LOCK > file for some time. > My method of closing gnucash is firstly to save the data and the close > using the menu. I always follow this process and never use the 'X' method. > > August 24, 2021 gnucash ver 4.6, I investigated using SQLlite instead of > the compressed XML for data storage. > SQLite worked but the resultant file(s) were much larger than the XML > compressed version so I decided to continue to use the compressed XML. > > From that date (August 24, 2021) to today I still get gnucash > intermittently not removing the LOCK file. > This includes ver4.7, ver4.8 and ver4.9. It may happen ver4.6 but unsure. > Ever time I updated I hoped it would resolve the issue but it still > happens. > About 20 days ago I deleted the SQL subdirectory and files from my local > data disk. This seemed to make no difference to the issue. > > > > On 19/01/2022 06:17, gnucash-user-requ...@gnucash.org wrote: > > Send gnucash-user mailing list submissions to > > gnucash-user@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-requ...@gnucash.org > > > > You can reach the person managing the list at > > gnucash-user-ow...@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: Exiting GNUCash (D.) > > 2. Re: Exiting GNUCash (David Carlson) > > 3. OneDrive (men...@fastmail.fm) > > 4. Re: gnucash-user Digest, Vol 226, Issue 48 (Heide Wang) > > 5. Re: OneDrive and GnuCash (davidcousen...@gmail.com) > > > > ___ > > > > 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. > ___ 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] Exiting gnucash Lock file Vol 226, Issue 57
This is interesting. I have had this problem of gnucash intermittently not removing the LOCK file for some time. My method of closing gnucash is firstly to save the data and the close using the menu. I always follow this process and never use the 'X' method. August 24, 2021 gnucash ver 4.6, I investigated using SQLlite instead of the compressed XML for data storage. SQLite worked but the resultant file(s) were much larger than the XML compressed version so I decided to continue to use the compressed XML. From that date (August 24, 2021) to today I still get gnucash intermittently not removing the LOCK file. This includes ver4.7, ver4.8 and ver4.9. It may happen ver4.6 but unsure. Ever time I updated I hoped it would resolve the issue but it still happens. About 20 days ago I deleted the SQL subdirectory and files from my local data disk. This seemed to make no difference to the issue. On 19/01/2022 06:17, gnucash-user-requ...@gnucash.org wrote: Send gnucash-user mailing list submissions to gnucash-user@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-requ...@gnucash.org You can reach the person managing the list at gnucash-user-ow...@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: Exiting GNUCash (D.) 2. Re: Exiting GNUCash (David Carlson) 3. OneDrive (men...@fastmail.fm) 4. Re: gnucash-user Digest, Vol 226, Issue 48 (Heide Wang) 5. Re: OneDrive and GnuCash (davidcousen...@gmail.com) ___ 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.
