Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

After refresh UBUNTU modifications 3.2 add-on still present. Why?

  • 2 válasz
  • 1 embernek van ilyen problémája
  • 1 megtekintés
  • Utolsó üzenet ettől: harry.nelsen

more options

The plugins have all been disabled but this extension has not after I have reset Firefox to default. I'm concerned because I'm trying to deal with what is said to be malware (secure-ds.serving-sys.c...) that is appearing as an unresponsive script.

The plugins have all been disabled but this extension has not after I have reset Firefox to default. I'm concerned because I'm trying to deal with what is said to be malware (secure-ds.serving-sys.c...) that is appearing as an unresponsive script.

Összes válasz (2)

more options

When you install Firefox distributed by a third party, the third party sometimes modifies the bundle. You may find that it's normal for your distribution to have that extension (as a Windows user, I wouldn't know). You certainly could disable it if you like.

Regarding the script error, did this article pop up during your question submission: Warning Unresponsive script - What it means and how to fix it. I'm not sure about the malware warning, that may be coming from a different program.

more options

No, I was resetting to defaults because when searching for info on the unresponsive script I was told that unidentified browser add-ons were likely sources of this malware. (secure-ds.serving-sys.c ... .js) When UBUNTU modifications 3.2 wasn't disabled with the rest of the add-ons, it made me suspicious. I don't know yet if the problem has returned.