logins.json.corrupt has zero length - opensuse linux
I've been having a reoccurring problem with my passwords disappearing. This is not the common .corrupt problem. All logins.json* files are truncated to zero length, including my backup.
-rw------- 1 david42 users 1151 Oct 5 13:49 logins.json -- this is the newly created file holding my login here and my email account. -rw------- 1 david42 users 0 Sep 30 10:18 logins.json.09302019 -rw------- 1 david42 users 0 Sep 30 14:35 logins.json-1.corrupt -rw------- 1 david42 users 0 Sep 30 14:37 logins.json-2.corrupt -rw------- 1 david42 users 0 Oct 5 13:27 logins.json-3.corrupt -rw------- 1 david42 users 0 Sep 30 11:22 logins.json.corrupt
This is linux so the AVG problem doesn't apply.
NAME="openSUSE Leap" VERSION="15.0" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.0" PRETTY_NAME="openSUSE Leap 15.0" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.0" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/"
Firefox 60.8.0esr (64-bit)
I've upgraded to 68.1.0(asr), so maybe the problem will go away. Close the ticket and if I need to I will start another one.Leggere questa risposta nel contesto 0
Dettagli aggiuntivi sul sistema
- User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
In the event that the passwords information is lost, you should record all information in a separate text file somewhere else on your hard drive, or written down. You can easily copy and paste if you need to do so. If you are concerned about someone else looking at that file, you can compress it using a password.
Look on your desktop. Do you see a folder called; Old Firefox? Look inside. Look for the folder with the latest creation date.
Maybe try to remove pkcs11.txt and secmode.db to see if that has effect.
Did you check for issues with the key file (currently key4.db, previously key3.db) ?
Utente che ha posto la domanda
Fred - there is no way to dump the password file in text form any more. Nor is there an old firefox directory. Nor are there any other profiles. Let me repeat: the login file is not only being renamed, it is being truncated to zero length. I have reviewed several dozen cases of problems with firefox and logins and nothing matches this problem. No one has reported the file being truncated.
cor-el - how would I know there is a problem with key4.db? Both key3.db and key4.db haven't been touched by the OS since May 10, 2018.
Utente che ha posto la domanda
cor-el there is no secmode.db. I renamed pkcs11.txt and restarted firefox. the new file is identical to the old one. key4.db opens without a problem in mysql, so structurally it's fine.
Thanks for the ideas, though.
This is not about the structure of key4.db (SQLite database), but about the encryption key (initial seed and possible master password) that are required to encrypt and decrypt data stored in logins.json. If the key file doesn't match or the content is otherwise corrupted then Firefox won't be able to store login data.
You can try to rename both logins.json and key4.db files with Firefox closed and let Firefox create new files to see if that works.
I've upgraded to 68.1.0(asr), so maybe the problem will go away. Close the ticket and if I need to I will start another one.