Robert Heller wrote:
If you improperly close Gnucash it will leave behind a lock file, which
Gnucash takes to mean that Gnucash already running -- Gnucash does not support
multiple concurrent instances using the same datafile and checks for this
case. Improperly closing Gnucash happens when you d
P.S. I forgot to mention that I am running the same version of GnuCash
as you on Windows 10 and not experiencing the problems you described,
albeit I have it installed on the C:\ drive and do not use DropBox.
Version: 5.8
Build ID: 5.8+(2024-07-06)
Finance::Quote: 1.49
Good luck!
Regar
Thank you, Geoff - then SourceForge is the place to go...
I have (re)noted the installation process and latest released version
information - this time more obviously in my documentation.
I had wondered at the instances on GitHub... SourceForge for me! LOL!
Thanks!
Megan in Sydney
On Thu,
Hi Megan
There is no guarantee that an upgrade will fix your particular problem,
however to answer your questions:
> If I need to update the GC program:
>
> 1. where do I find the documentation outlining the process and
> 2. where do I source the most recent release
>
The installation
My apologies - I did forget to include the App version data:
Windows 10 Home 64-bit
Version 22H2
OS build 19045.5011
GnuCash
Version: 5.8
Build ID: 5.8+(2024-07-06)
Finance::Quote: 1.62
== I am the only user.
== I only use GnuCash on this computer.
== This issue started on Oct 26 with the first
She is running Windows 10 (she said in her original post; see what I kept
below)... but not sure which version of GnuCash is being used.
Robert, note that there was a GnuCash bug in the Windows version that left
a process running that caused this problem.
On Wed, Oct 30, 2024 at 8:48 AM Robert H
You don't need to save as a new name.
The fact that there was a LCK file with the new name implies that you have
the version with the bug that didn't fully shut down GnuCash when one does
File->Quit. What version of GnuCash are you running? If you are not at 5.8
or 5.9, I strongly recommend updati
Yes, if "GC closing down by itself (as in - a failure of the app)" -- that is
it is "crashing", the LOCK will be left behind.
It sounds like something is wrong. *I* know nothing about MS-Windows. Can
you post here the exact version of Gnucash and the version of MS-Windows you
are running? Som
At Wed, 30 Oct 2024 11:59:41 -0500 R Losey wrote:
>
> She is running Windows 10 (she said in her original post; see what I kept
> below)... but not sure which version of GnuCash is being used.
>
> Robert, note that there was a GnuCash bug in the Windows version that left
> a process running that
On 2024-10-29 17:19, Robert Heller wrote:
> Generally, you can select "Open Anyway". But it is best to avoid this
> by properly exiting Gnucash: File=>Exit.
More specifically, you can safely click "Open Anyway" if your data file
is on this computer (as opposed to some sort of network or cloud
sto
Hi Megan
> I received the same error message but this time chose "Open Anyway".
> My file opened and I immediately SAVED AS a new file name.
Good.
> I looked at the folder where my data is stored and there is a LOCK
> file with the new name (formatted as ".gnucash.LCK") in the folder
> with
Hi Robert,
I rebooted again and tried to open GC.
I received the same error message but this time chose "Open Anyway".
My file opened and I immediately SAVED AS a new file name.
I did what I needed to do (TRansaction Report), and closed GC down.
I looked at the folder where my data is stored and
If you have rebooted your computer since you've last run GnuCash and you
know that GnuCash is not running on any other computer accessing that file,
you may safely use the "Open anyway" option - it seems to deleted the old
.LCK file, create a new one, and open your file.
On Tue, Oct 29, 2024 at 9:
You can also delete the .LCK file and the message will go away.
Will
On 29 Oct 2024, at 20:14, Geoff wrote:
Have you tried "Open Anyway"?
On 30/10/2024 1:12 pm, Megan Tilley wrote:
> Thanks, Robert. Apparently, unlike most Windows Users you may be acquainted
> with, I almost always shut down a
As has been noted, it means that GnuCash thinks that another instance of
GnuCash still has the file open. This could be very dangerous unless you
KNOW that something happened -- such as GnuCash crashing, or Windows being
shut down while it was running.
Also, note, you didn't say which version of G
Have you tried "Open Anyway"?
On 30/10/2024 1:12 pm, Megan Tilley wrote:
Thanks, Robert. Apparently, unlike most Windows Users you may be acquainted
with, I almost always shut down any program I am using once finished.
In this particular case, I know I shut GnuCast down. However, I DID try and
Thanks, Robert. Apparently, unlike most Windows Users you may be acquainted
with, I almost always shut down any program I am using once finished.
In this particular case, I know I shut GnuCast down. However, I DID try and
reopen it within 60 seconds of shutting GC down. I think that is the cause
o
If you improperly close Gnucash it will leave behind a lock file, which
Gnucash takes to mean that Gnucash already running -- Gnucash does not support
multiple concurrent instances using the same datafile and checks for this
case. Improperly closing Gnucash happens when you do something like shutdo
Hi everyone, I occasionally receive this message, but I can not find its
definition anywhere.
I am the only user on this Win10 platform, and if GC is closed, and does
not appear in TaskManager, isn't it "closed"?
My options are to - Open Read-only; create New file; Open Anyway; Open
Folder.
1) w
19 matches
Mail list logo
