-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on unsaved new database, all logins gone !! #105
Comments
I did follow your steps:
But it did not crash. A warning dialog appeared to remind the user that there are unsaved changes. Your error message indicates rather that the "LockDatabase" procedure is causing the issue and indeed I can confirm the bug which caused your data loss. If the keep-backup-file flag is set in the preferences and if the database is locked then this error will be produced because in this early stage there is no filename for the database but only a copy in the memory. I am sorry for this bug but a patch will immediately close this early stage hole. The next version 1.5.3.7 will have fixed this bug. |
Makes sense! I did have backup enabled. I suppose the bug fix will prompt for a filename when the backup happens and no filename is yet available. Thanks for the timely response. I'm all in as user of Gorilla! |
"I suppose the bug fix will prompt for a filename when the backup happens and no filename is yet available." Yes, it does so. Commit 203b4a3 will show you details. " I'm all in as user of Gorilla!" You are welcome :-) |
https://github.com/downloads/zdia/gorilla/gorilla15363.exe
Maybe something wrong with saving the new database for the first time?
If I did "save as" some file in step 4, it does not crash.
In general, how reliable the Executable Starkits of Password Gorrila is? This is scary..
The error log reads:
can't read "::gorilla::fileName": no such variable
can't read "::gorilla::fileName": no such variable
while executing
"gorilla::SaveBackup $::gorilla::fileName "
(procedure "LockDatabase" line 41)
invoked from within
"LockDatabase"
(procedure "::gorilla::IdleTimeout" line 2)
invoked from within
"::gorilla::IdleTimeout"
("after" script)
The text was updated successfully, but these errors were encountered: