Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

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

  • 2 wótegronje
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót 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.

Wšykne wótegrona (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.