Firefox-Hilfeforum

On the page listing passwords, it was possible to sort them by "Alerts".

In settings, there is an option to enable checking the vulnerable passwords: https://support.mozilla.org/en-US/kb/firefox-password-manager-alerts-breached-websites

On my other laptop using Firefox v121, the alerts are properly displayed. But on my second laptop using Firefox v124, the alerts are gone. I can't sort password by "Alerts", the option isn't there. Both laptops share the same Firefox account and have password synchronized between each other.

Obviously, I ticked the "Show alerts about passwords for breached websites" box in the settings but it looks like it does not nothing. I also checked in "about:config" and everything seems good.

Is this feature gone?

Please see the attached image.

Firefox believes I have a security key.

What is a security key? Where do I find it? Why does Firefox think I have one?

And why is there no helpful information to explain this confusing UX?

Currently, I use Firefox version: 116.0.2 on Ubuntu 20.04.6 LTS.

I encountered a phenomenon like this:

• When I logged in to the application, in the tab I was working on, the Firefox session memory was lost (don't open new tabs)

What is the cause of this phenomenon? How can I fix it?

Hello Good People,

I noticed that the snap version of Firefox had a lag issue when typing into input field. For example, when composing an email and wanting to use backspace to quickly delete a misspelled word, then backspace works slowly, stuttering and jittering. If I hold down a key in the input field it also lays the character down in a stuttery, slow way.

I tried reinstalling the system and that solved the issue. But it has returned again. Maybe it was an update. I also installed WINE and waybridge to get some windows plugins to work on my DAW. I don't know if that has affected it.

I also tried removing the snap version and installing firefox using the terminal but the problem persisted.

It's an annoying problem. Any advice appreciated.

Currently, I use Firefox version: 116.0.2 or v117.0 on Ubuntu 20.04.6 LTS.

I encountered a phenomenon like this:

• When I logged in to the application, in the tab I was working on, the Firefox session memory was lost (don't open new tabs)

Steps: 1. Login to the application 2. Operate on the screen 3. Navigate to other URLs, but still on this tab 4. Session storage was lost

What is the cause of this phenomenon? How can I fix it?

latest 124.0.2 causing severe problems, it will near instantly bloat to fill all RAM and SWAP even in safe mode causes system load over 24! only solution is to reboot very problematic on for ex: https://epg.pw/xmltv/epg_CA.xml hard to get a screencap since system is nearly totally unresponsive. RAM is ok SSD is ok MX Linux is ok

Issue: The "Recommended stories" setting for the new tab default home page periodically re-enables itself.

Version Info: Firefox 124.0.1 (64-bit) OS: Linux Mint 21.1 Cinnamon

Additional Information:

• I do not use pocket, at all
• All settings that I can find related to pocket are disabled
• I do use Firefox Sync, however the other device (124.0.1 (64-bit) on pop_os!) does not have this issue
• Does not correlate to version updates (Mint has automatic updates disabled in policies)
• Does not occur after a simple restart

I am tired of disabling this setting and having it return seemingly randomly. I have no interest in these stories, and consider them spam.

Please assist me in determining why this is happening on this device and how we can go about preventing it going forward.

Thanks, Steven

Lately, when I try to download different files like .docx, .pptx, etc., Firefox always downloads files with a .pdf extension. I tried it in a different browser, and the problem does not occur there. Of course, the files are the same in binary terms, so when I change the extension, everything is fine, but it is annoying. What is wrong?

Firefox version 124.0.2-1 latest/stable OS: Ubuntu 23.10 Kernel: Linux 6.5.0-26-generic

Actually my problem was solved. It came from the fact that following a maintenance intervention on the servers of the https site where my account was located, and access to which was blocked by Mozilla, the automatic updating of certificates had not worked. Which the site technicians resolved following a request I sent to them.