Open Bug 1992571 Opened 1 year ago Updated 2 months ago

Credit card auto-fill not working / getting insta-cleared.

Categories

(Toolkit :: Form Autofill, defect, P3)

defect

Tracking

()

ASSIGNED

People

(Reporter: emilio, Assigned: simonf)

References

Details

On my current profile autofilling a credit card, even something like https://mozilla.github.io/form-fill-examples/basic_cc_2.html doesn't work at all. The options and the preview show up but clicking on the popup clears the form.

This seems to happen on release as well so I assume something specific to my profile?

With autofil.loglevel=Debug:

FormAutofillSection: Reauth is disabled FormAutofillSection.sys.mjs:691
OSKeyStore: Decryption failed with result: 2147500037 OSKeyStore.sys.mjs:325
FormAutofillParent: profile cannot be filled

Dimi you seem familiar with this code, any idea what might be going on?

Flags: needinfo?(dlee)

(This is on Linux)

(In reply to Emilio Cobos Álvarez [:emilio] from comment #0)

This seems to happen on release as well so I assume something specific to my profile?

This is probably related to Bug 1755786. The issue occurs when the key stored in OSKeyStore is removed. When we can access the key in OSKeyStore and we cannot access for some reason, we recreate a new one, which causes the credit card information encrypted with the old key is no longer available.
We recently fixed a case on macOS where we would overwrite the key when a user chose “Deny” in the Keychain prompt.

Simon, this issue is on Linux. Do you have a hypothesis for the root cause, or is there any information Emilio could provide to help us debug?

Flags: needinfo?(dlee) → needinfo?(sfriedberger)

For context, the general problem here is, that it is very difficult to tell a transient key store failure from a permanent one.
If the failure is permanent, we should delete the data and start over because the user can never get it back anyway. If the failure is transient we need to fail this particular operation but not delete any data. Unfortunately, the APIs make that hard.

I would be interested in:

  • Which keystore are you using? Gnome, KDE, something else? Or do you maybe not have one installed at all and this is falling back to the internal NSS key store?
  • Do you ever get any prompts for access to secrets that you might have denied?
  • Did you switch Firefox versions at some point such that access to secrets might be allowed based on application and the new one does not have access? (I don't think Linux support this.)
Flags: needinfo?(sfriedberger)
Flags: needinfo?(emilio)
See Also: → 1976610
Assignee: nobody → sfriedberger
Status: NEW → ASSIGNED

(In reply to Simon Friedberger [:simonf] from comment #4)

  • Which keystore are you using? Gnome, KDE, something else? Or do you maybe not have one installed at all and this is falling back to the internal NSS key store?

I'm using KDE. My guess is that when I initially ran this nightly I still didn't have the key store installed, and then I installed it. Would that cause the issue?

  • Do you ever get any prompts for access to secrets that you might have denied?

No

  • Did you switch Firefox versions at some point such that access to secrets might be allowed based on application and the new one does not have access? (I don't think Linux support this.)

No, this is only on Nightly. I have a release profile which is also affected tho.

Flags: needinfo?(emilio)

The severity field is not set for this bug.
:dimi, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dlee)
Severity: -- → S3
Flags: needinfo?(dlee)
Priority: -- → P3
See Also: → 2026488

On Ubuntu 26.04/GNOME with gnome-keyring, a card encrypted 2026-05-06 stopped decrypting after switching Firefox packaging (Ubuntu snap → mozillateam deb).
Eventually, it occurred to me that this bug wasn't getting fixed, so I deleted the stored card and re-entered it.
Then it worked.
The bug, then, IMO, is a UI problem. Instead of showing the saved card, then
clearing the form when it can't be accessed or decrypted because how it was
stored no longer matches the way the current Firefox is accessing it,
it should warn something like, "this saved card can no longer be decrypted, remove it?"

You need to log in before you can comment on or make changes to this bug.