GNUcash crashes on save - losing all changes

[Derek Atkins]

I'll note that GnuCash does not have the concept of opening a data
file as "read-only"...  So, providing an "open as read-only" and "open
normally" doesn't do anything, because as far as gnucash is concerned
they are the same.

Note that the current string is:

		 _("GnuCash could not obtain the lock for\n"
		   "   %s.\n"
		   "That database may be in use by another user,\n"
		   "in which case you should not open the database.\n"
		   "\nWhat would you like to do?") :

In other words, it _DOES_ say that "that database may be in use by
another user."

As for being more proactive about removing the lockfile, I'm a bit
torn about that.  What happens if you try to exit gnome but still have
unsaved changes in gnucash?  I do agree that gnucash should clean up better
on a "clean" shutdown, but I'm still not convinced that exiting gnome
is necessarily a clean shutdown.  Is Ctl-Alt-Backspace a clean shutdown?
What about a power outage?

-derek

Vincent V <vincentv at dsl.pipex.com> writes:

> Done
> 
> you will find it under the bugzilla sumary of
> BiIl Wohler  Re: GNUcash crashes losing all changes
> 
> Vince
> 
> 
> Bill Wohler wrote:
> 
> >Chris Shenton <chris at shenton.org> writes:
> >
> >
> >>Vincent V <vincentv at dsl.pipex.com> writes:
> >>
> >>
> >>>If the files exist then the user should be warned that 'The accounts
> >>>file seems to be in use' (rather than the cryptic 'GNUcash could not
> >>>obtain the lock' - which is only meaningful to the developers) and
> >>>given the choice to 'Open as read-only' or 'If you are sure that no
> >>>one else is using it then Open Normally'
> >>>
> >>I like this last one :-)
> >>
> >
> >I agree, this verbiage is better.
> >
> >Note that I save early and save often, and sometimes exit Gnome without
> >quitting gnucash, so I get this warning quite often. In addition to
> >using a more user-centric message, we can do better.
> >
> >Since the files might be accessed via NFS, gnucash can't simply check
> >the lock file and see if there is a gnucash process with the given PID
> >or not. So, gnucash needs to do a better job cleaning up the lock file.
> >The lock file should be removed any time gnucash goes away, so in
> >addition to normal exit, gnucash should catch SIGHUP and SIGTERM and
> >remove the lock files if those signals are caught.
> >
> >I'm--um--on a sailboat in Hawaii right now and this message is only
> >getting to you because I managed to find a network for a few seconds. If
> >someone would be kind enough to put the previous paragraph in bugzilla,
> >I'd appreciate it.
> >
> >--
> >Bill Wohler <wohler at newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
> >Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
> >If you're passed on the right, you're in the wrong lane.
> >
> >
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at lists.gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available