This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

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

  • 2 valiny
  • 1 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i 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.

All Replies (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.