Cool, glad you got it sorted.

Cheers David H.


On Sun, 10 Mar 2024 at 03:09, Eric H. Bowen via gnucash-user <
gnucash-user@gnucash.org> wrote:

> David/john:
>
> Thanks for the helpful replies. After you mentioned it, I remembered the
> auto-history version save of my NAS-based cloud drive. Upon checking in
> there, I found two versions which had saved within two seconds of each
> other at the time I attempted to switch books. The second one, which
> Windows saw, was the corrupted file but the two-seconds-earlier version
> was uncorrupted and loaded properly. I flushed the corrupted version and
> now I'm back in business. Thanks again----Eric.
>
> On 3/9/2024 9:25 AM, gnucash-user-requ...@gnucash.org wrote:
> > Send gnucash-user mailing list submissions to
> >       gnucash-user@gnucash.org
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 9 Mar 2024 07:43:24 +1000
> > From: David H <hell...@gmail.com>
> > To: "Eric H. Bowen" <e...@ehbowen.net>
> > Cc: gnucash-user@gnucash.org
> > Subject: Re: [GNC] GnuCash Will Not Open Book After Changing Books
> >       (Bug 645216)
> > Message-ID:
> >       <
> ca+5xqdq5tyik_yhk-b3qpgdrxzk-woclq9mvj-s9p5qgyvk...@mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Eric,
> >
> > Are you sure you haven't got a more recent backup?  I have multiple
> backups
> > (currently 77 - e.g. <gnucash file name>.gnucash.20240208183810.gnucash)
> in
> > the folder where my usual gnucash data file lives from the last time I
> > opened it - you should be able to open the one with the most recent date
> > and time stamp in the name and then save as you LLC file proper. .  It
> > seems you are opening this file directly in the cloud - I've never been a
> > fan of that ? I always copy my file to my local pc (1 of about 5 running
> > Win10/11, Ubuntu, MacOS) using FreeFileSync before I open it and then
> copy
> > it back when I'm done which works well for me.  Hope you can get it
> sorted.
> >
> > Cheers David H.
> >
> >
> > On Fri, 8 Mar 2024 at 23:59, Eric H. Bowen via gnucash-user <
> > gnucash-user@gnucash.org> wrote:
> >
> >> I use two separate GnuCash books, one for my personal funds and another
> >> for my LLC. These files are saved on a cloud drive and I access them
> >> from a few different computers. Some of the computers run Windows 10,
> >> while some run Ubuntu Studio 22.04 LTS. The computer on which this first
> >> happened was running Windows 10 and GnuCash 5.4+ with sqlite backend,
> >> but all computers are now responding the same way.
> >>
> >> The day before yesterday I was updating and making some entries in the
> >> book for my LLC; GnuCash was working normally. Then, with the work
> >> completed, I attempted to switch from the LLC book to my personal book.
> >> However, apparently the file was still open on a remote computer because
> >> I received the error message that the .lock file could not be received.
> >> I elected to close the file and exit GnuCash. Well and good. When I got
> >> home that evening I closed the open instance of GnuCash running the
> >> personal book. Well and good.
> >>
> >> This morning I reopened the personal book and it opened and operated
> >> normally. Okay so far. Then, I closed it and attempted to open the book
> >> for the LLC. It would not open; I got a pop-up error message reading,
> >> "GnuCash could not complete a critical test for the presence of a bug in
> >> the "libdi" library. This may be caused by a permissions
> >> misconfiguration of your SQL database. Please see
> >> https://bugs.gnucash.org/show_bug.cgi?id=645216 for more information."
> >>
> >> I went to the bug tracker website, found the entry, and attempted to
> >> follow the procedure which others said worked for them, of making a copy
> >> of the GnuCash file and opening/closing it. However, the copied file(s)
> >> were also corrupt and would not open. I do have a backup, but it's a few
> >> weeks old and I'd have to reconstruct the invoices and bills since then.
> >> Not a major undertaking, but if possible I'd like to recover this file.
> >> The personal book, by the way, continues to work perfectly. Thanks for
> >> any assistance----Eric.
> >>
> >>
> >> _______________________________________________
> >> 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.
> >>
> >
> > ------------------------------
> >
> > Message: 9
> > Date: Sat, 9 Mar 2024 16:17:45 +0100
> > From: john <jra...@ceridwen.us>
> > To: David H <hell...@gmail.com>
> > Cc: "Eric H. Bowen" <e...@ehbowen.net>, gnucash-user@gnucash.org
> > Subject: Re: [GNC] GnuCash Will Not Open Book After Changing Books
> >       (Bug 645216)
> > Message-ID: <b3540e18-38b3-4851-ba26-adf9d83a1...@ceridwen.us>
> > Content-Type: text/plain;     charset=us-ascii
> >
> > Are you using the SQLite3 backend? If so and it's really corrupted see
> https://www.sqlite.org/recovery.html. Good luck.
> >
> > Regards,
> > John Ralls
> >
> >
> >
> >> On Mar 8, 2024, at 22:43, David H <hell...@gmail.com> wrote:
> >>
> >> Eric,
> >>
> >> Are you sure you haven't got a more recent backup?  I have multiple
> backups
> >> (currently 77 - e.g. <gnucash file
> name>.gnucash.20240208183810.gnucash) in
> >> the folder where my usual gnucash data file lives from the last time I
> >> opened it - you should be able to open the one with the most recent date
> >> and time stamp in the name and then save as you LLC file proper. .  It
> >> seems you are opening this file directly in the cloud - I've never been
> a
> >> fan of that ? I always copy my file to my local pc (1 of about 5 running
> >> Win10/11, Ubuntu, MacOS) using FreeFileSync before I open it and then
> copy
> >> it back when I'm done which works well for me.  Hope you can get it
> sorted.
> >>
> >> Cheers David H.
> >>
> >>
> >> On Fri, 8 Mar 2024 at 23:59, Eric H. Bowen via gnucash-user <
> >> gnucash-user@gnucash.org> wrote:
> >>
> >>> I use two separate GnuCash books, one for my personal funds and another
> >>> for my LLC. These files are saved on a cloud drive and I access them
> >>> from a few different computers. Some of the computers run Windows 10,
> >>> while some run Ubuntu Studio 22.04 LTS. The computer on which this
> first
> >>> happened was running Windows 10 and GnuCash 5.4+ with sqlite backend,
> >>> but all computers are now responding the same way.
> >>>
> >>> The day before yesterday I was updating and making some entries in the
> >>> book for my LLC; GnuCash was working normally. Then, with the work
> >>> completed, I attempted to switch from the LLC book to my personal book.
> >>> However, apparently the file was still open on a remote computer
> because
> >>> I received the error message that the .lock file could not be received.
> >>> I elected to close the file and exit GnuCash. Well and good. When I got
> >>> home that evening I closed the open instance of GnuCash running the
> >>> personal book. Well and good.
> >>>
> >>> This morning I reopened the personal book and it opened and operated
> >>> normally. Okay so far. Then, I closed it and attempted to open the book
> >>> for the LLC. It would not open; I got a pop-up error message reading,
> >>> "GnuCash could not complete a critical test for the presence of a bug
> in
> >>> the "libdi" library. This may be caused by a permissions
> >>> misconfiguration of your SQL database. Please see
> >>> https://bugs.gnucash.org/show_bug.cgi?id=645216 for more information."
> >>>
> >>> I went to the bug tracker website, found the entry, and attempted to
> >>> follow the procedure which others said worked for them, of making a
> copy
> >>> of the GnuCash file and opening/closing it. However, the copied file(s)
> >>> were also corrupt and would not open. I do have a backup, but it's a
> few
> >>> weeks old and I'd have to reconstruct the invoices and bills since
> then.
> >>> Not a major undertaking, but if possible I'd like to recover this file.
> >>> The personal book, by the way, continues to work perfectly. Thanks for
> >>> any assistance----Eric.
> >>>
> >>>
> >>> _______________________________________________
> >>> 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.
> >>>
> >> _______________________________________________
> >> 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.
> >
> >
> > ------------------------------
> >
> > Message: 10
> > Date: Sat, 9 Mar 2024 16:25:37 +0100
> > From: john <jra...@ceridwen.us>
> > To: Jack Slater <theillini...@gmail.com>
> > Cc: David H <hell...@gmail.com>, Gnucash Users
> >       <gnucash-user@gnucash.org>
> > Subject: Re: [GNC] Maddening!!!!!!!!
> > Message-ID: <3126fe1b-2ef7-4c4b-b5b0-f1f871db7...@ceridwen.us>
> > Content-Type: text/plain;     charset=utf-8
> >
> > No, that's a re-bundling of GnuCash 5.5 for Windows with a rebuilt
> WebKitGtk so that it doesn't crash when you try to run a business or chart
> report. There are no changes to GnuCash itself.
> >
> > The fix for the left-over splits from editing an auto-completed
> transaction will be in GnuCash 5.6. Flatpak and Windows users can get it
> from a nightly build, otherwise you have to wait a few weeks.
> >
> > But we now know that it's caused by a dangling pointer in the account's
> split list from a second run of autocomplete. You can safely ignore
> it--meaning don't check it when reconciling--and it will go away when you
> end the session.
> >
> > Regards,
> > John Ralls
> >
> >> On Mar 9, 2024, at 02:00, Jack Slater <theillini...@gmail.com> wrote:
> >>
> >> Oh ok. Happy to. I guess I was expecting a 5.51 or something to
> >> differentiate the releases.
> >>
> >> On Fri, Mar 8, 2024 at 4:09?PM David H <hell...@gmail.com> wrote:
> >>
> >>> Jack,
> >>>
> >>> John Ralls released an updated version of 5.5 on 21 Feb -
> >>>
> https://lists.gnucash.org/pipermail/gnucash-user/2024-February/110886.html
> >>> - I assume if you re-download the Windows version at Gncash.org you
> will
> >>> pick it up ?
> >>>
> >>> Cheers David H.
> >>>
> >>> On Sat, 9 Mar 2024 at 04:57, Jack Slater <theillini...@gmail.com>
> wrote:
> >>>
> >>>> Revisiting the bug log (after another rogue transaction and crash
> today)
> >>>> and I see John's notes about fixing but I'm guessing it's not in 5.5?
> >>>> That's what I'm running and all I see on the web site.
> >>>>
> >>>> On Thu, Feb 8, 2024 at 11:12?AM Patrick James <
> patrickjame...@comcast.net
> >>>> wrote:
> >>>>
> >>>>> Save, Exit, and Reload will clear the rouge transactions.
> >>>>>
> >>>>>
> >>>>>> On 02/08/2024 8:54 AM PST Jack Slater <theillini...@gmail.com>
> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Anything coming soon to fix this?
> >>>>>>
> >>>>>> On Thu, Jan 25, 2024 at 12:26?PM Patrick James <
> >>>>> patrickjame...@comcast.net mailto:patrickjame...@comcast.net> wrote:
> >>>>>>> This is bug 799093, and John Ralls has not asked additional
> >>>> questions
> >>>>> after I was able to reliably reproduce (part of) the issue, so,
> >>>> hopefully,
> >>>>> there is sufficient information to find the bug.
> >>>>>>> https://bugs.gnucash.org/show_bug.cgi?id=799093
> >>>>>>>
> >>>>>>> s 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.
> >>>>>
> >>>> _______________________________________________
> >>>> 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.
> >>>>
> >> _______________________________________________
> >> 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.
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> >
> > 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.
> >
> >
> > ------------------------------
> >
> > End of gnucash-user Digest, Vol 252, Issue 21
> > *********************************************
> _______________________________________________
> 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.
>
_______________________________________________
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.

Reply via email to