We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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

  • 2 відповіді
  • 1 має цю проблему
  • 1 перегляд
  • Остання відповідь від 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.

Усі відповіді (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.