Page 2 of 2
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Sun Jan 01, 2012 6:29 pm
by ptoye
I have a similar problem, reported in
http://forums.informaction.com/viewtopic.php?f=7&t=7943 so it seems that there is a genuine NoScript (or Firefox) problem. This one might be a process hanging when FF is closed down by a system shutdown.
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Mon Jan 02, 2012 1:40 am
by Tom T.
It's not necessary to double-post. The topic you started was replied to. (perhaps not instantly, but there was some sort of celebration over the past day or so.

)
As you saw in this thread, there was no Fx or NS problem. If there were, we'd probably have more than two reports in seven weeks.

The culprit was malware. 80-90% of home computers are infected with at least one malware, per random surveys. Let's close this discussion, and work on your original thread.
Cheers.
ETA: Hope that didn't come out the wrong way. This thread ended a little O/T, as some of us were doing the post-mortem.
Figured that the culprit was different, even though the diagnostics would be similar, so absent strong evidence that there is in fact a common bug, we might as well stay at your fresh topic. Again, it's that celebration-stuff.

Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Mon Jan 02, 2012 11:36 am
by ptoye
I didn't think that putting a link in counted as a double-post. And as this problem was malware I hope it's not significant to mine! So I'll get off this topic and back to my original one.
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Tue Jan 03, 2012 7:38 am
by Tom T.
ptoye wrote:I didn't think that putting a link in counted as a double-post.
As said in the after-thought, didn't mean that to sound negative at all. Sorry if it did.
And as this problem was malware I hope it's not significant to mine! So I'll get off this topic and back to my original one.
Let's hope not, but it could be. Back to the other, indeed.
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Fri Jan 06, 2012 7:57 am
by therube
that Spigot toolbar is malware
Where, how did "spigot" come into play in this thread?
Side note:
ctfmon.exe, while a legit MS process has been known to cause problems with particular apps. If you do not need it, many do not, cannot hurt to disable it.
Oh, & a PNG will generally give you a clearer screenshot the a JPG. Can't hurt to make it a bit bigger too

.
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Fri Jan 06, 2012 10:03 am
by Tom T.
therube wrote:that Spigot toolbar is malware
Where, how did "spigot" come into play in this thread?
In all three of his not-as-clear-as-PNG screenshots,

there was a process, Search Settings.exe, with a source of Spigot Inc.
I did a, what's the word? - oh, yeah, "Web search" for Spigot and found the thread that was linked in
my reply.
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Fri Jan 06, 2012 5:36 pm
by therube
Search Settings.exe, with a source of Spigot Inc
Thanks, I'd missed that.
(Actually what I did was, by default ignored all entries with a "Company Name", thinking a malware company isn't going to list their name, & by doing so blinded myself to it.)
Re: FF8.0 NoScript 2.1.9 -> Can't restart Firefox
Posted: Sat Jan 07, 2012 11:17 am
by Tom T.
therube wrote:(Actually what I did was, by default ignored all entries with a "Company Name", thinking a malware company isn't going to list their name, & by doing so blinded myself to it.)
How sneaky of them, mwahaha!
Seriously: Many "toolbars" or "search bars" are openly promoted. Sometimes, in the fine print in the EULA that no one ever reads, they'll tell you what info they're gathering on you.
Others come along when you do a legit d/l, and there's a box, default-checked, "Also install XYX toolbar". Isn't Adobe doing that? (Idk. I never use Adobe Reader.)
The forum thread claiming a backdoor Trojan puts this one a little far out there. Idk the outcome, or just how bad the situation was. At the very least, it was spyware, and perhaps was trying to keep-alive a connection to home, thus preventing the browser shutdown. OP never did post back, so we don't know what happened there.