Hmm is right. I just tried to duplicate the issue and couldn't. It
must be something a little more subtle, or GC got into some bad state.
On 3/5/22 12:53, john wrote:
Hmm.
I have for many years kept my books in an encrypted disk image (dmg) that I
back up on Google Drive. After a restart I have to remount the dmg, something I
occasionally forget to do before starting GnuCash and when I do GnuCash pops up
that dialog. I've always told it no. I usually quit GnuCash, mount the dmg, and
restart GnuCash, and GnuCash though I sometimes just mount the dmg and then use
the saved entry at the bottom of the File menu to open the book. Both have
always worked without a problem.
ISTR this has come up before. Are you not answering the dialog box at all,
leaving it displayed, when you try to open the book after mounting the share?
Regards,
John Ralls
On Mar 5, 2022, at 9:50 AM, brad <bradha...@fastmail.com> wrote:
I think I have this sorted out. I did try File->Open, but it didn't work. I
did know about the 'Known Mac Thing', so annoying.
Something not obvious, probably a bug. When GC fails to open the last file,
because it isn't there or the Sambashare hasn't been mounted yet, a GUI pops up
saying it could not be found, it's in the history list, do you want to remove it?
You must say yes. You must say yes even if you're going to open another file
with File->Open.
The steps to recreate: Start GC by clicking the app, before mounting the sambashare.
It fails. Don't click yes on the history list removal (because why would you,
you're going to mount the sambashare and use it). Mount the sambashare & attempt
to file->open the file. Fail.
Subsequent attempts to mount the sambashare before starting GC, or copying the
GC file to local hard drive will fail also, until saying 'Yes' remove the file
from the history list.
This probably doesn't have anything to do with the MAC OS update, that was a
distraction.
Thanks
On 3/4/22 20:25, D. wrote:
I'm not using a Mac anymore, but you should know that double clicking a file in
Finder will not open that file in GnuCash but will open the last opened file
instead. It is a Known Mac Thing.
You might want to try using File -> Open to see whether your File really won't
open...
On 3/4/22 22:03, Adrien Monteleone wrote:
If you are getting a crash, you should file it on bugs.gnucash.org and attach
your crash report there.
Also, check the wiki about obtaining a TraceFile. That might be helpful as well.
But first...
I'm guessing you can start GnuCash since it crashes on exit.
Can you navigate to File > Open and look for your file that way to reset the
last-known location?
Regards,
Adrien
On 3/4/22 8:07 PM, brad wrote:
Upgraded to 4.9. It still fails to open. Also when closing GC it crashes. I
don't know if the list will allow it, but I'll attach the crash report.
_______________________________________________
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.
