-
Notifications
You must be signed in to change notification settings - Fork 34
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
[BUG]: Could not open database error #278
Comments
What browser is this? |
Hallo Herr Wieschollek,Nein, keine „Sonderlocken“. Bis gestern hat’s funktioniert. In Chrome tuts weiterhin. FF aufMAC OS tut auch nicht. Viele Grüße Martin Wetterau Am 02.02.2024 um 12:36 schrieb M. Wieschollek ***@***.***>:
What browser is this?
Are you using any specific settings that could impact the extensions ability to use the IndexedDB browser functionality?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Signed-off-by: Marius David Wieschollek <passwords.public@mdns.eu>
In the telegram channel, a user reported that the extension will not work if the "always browse in private mode" setting is enabled. This could also happen if the "create history" settings is set to never. I have added a workaround to the nightly release that will just fall back to an in-memory database if it's unable to use the browser database feature. |
Dear Mr. Wieschollek,
i made a FireFox "factory reset" in the meantime and everythings is working
fine since then.
Thank you!
Kind regards,
Martin
…---------- Forwarded message ---------
Von: M. Wieschollek ***@***.***>
Date: Mi., 27. März 2024 um 14:59 Uhr
Subject: Re: [marius-wieschollek/passwords-webextension] [BUG]: Could not
open database error (Issue #278)
To: marius-wieschollek/passwords-webextension <
***@***.***>
Cc: Maddiehn22 ***@***.***>, Author <
***@***.***>
In the telegram channel, a user reported that the extension will not work
if the "always browse in private mode" setting is enabled. This could also
happen if the "create history" settings is set to never.
I have added a workaround to the nightly release that will just fall back
to an in-memory database if it's unable to use the browser database feature.
In that case you will now see the warning "Persistent database not
available. Maybe always private browsing is enabled?" in the extension
logs. And suggested passwords will not be as good as there is no
recommendation data.
—
Reply to this email directly, view it on GitHub
<#278 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6XPA22EXRE7TMALUC6FX5TY2K7EXAVCNFSM6AAAAABCWMPTZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRSHA2DKNZTGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Server Information
Client Information
Browser and Version:115.7.0 est
Client OS and Version: WIN7
Extension Version: 2.6 & 2.5
Bug description
Extension reports : Could not open database
Steps to reproduce
Open a password protected website
No password and usser will be inserted
Expected behavior
No automatic password insert works
No search works
Extension Logs
The text was updated successfully, but these errors were encountered: