InformAction Forums

I had to downgrade FF from 69.0 to 60.7.2esr on a linux machine recently.
Now, after quitting FF, the FF processes do not terminate fully anymore. In fact, a /usr/lib64/firefox/firefox job remains and has to be killed explicitly.

After consecutively disabling all add-ons within the pre-existing user profile, it turns out that only with NoScript enabled, FF will not terminate properly. Removing NoScript from the pre-existing user profile and re-installing did not help.

Starting FF on that machine from a fresh dummy profile or in safe mode does not lead to this issue.
Strangely however, including NoScript into the fresh dummy profile, FF will still terminate properly.

So it seems as if 'something' in the pre-existing user profile persists after the downgrade and conspires with NoScript to generate this issue?

What is this? How can I fix it?
Thx. Gerd.

(backup first)


Mozilla does not support "downgrade" routes.

Not sure why you're using 60.7.2esr when 60.9.0esr exists (perhaps not in your distro?)?

Might look into creating a new, clean Profile, then migrating wanted data from old to new?
(Then install extensions...)

Or removing, then reinstalling NoScript (in case that may happen to "fix" things)?

Certainly possible that particular versions of NoScript only support particular versions of FF.
(As in over time NoScript has incorporated features that newer FF support, that were not available at an earlier time, say with FF 60.0esr.)

Are you running Firefox in some kind of sandbox, e.g. firejail?