InformAction Forums

Thanks, I used your files to set up a minimal testcase for reproducing, but the bug is still unreproduible for me
I guess the only way is observing the "live thing". Is there any chance for me to do it?

Giorgio Maone wrote:Thanks, I used your files to set up a minimal testcase for reproducing, but the bug is still unreproduible for me
I guess the only way is observing the "live thing". Is there any chance for me to do it?

I appreciate the need to see it "live" for further diagnostics. I understand the difficulty in identifying what changed bwtween 1.95 and 1.967 coupled with streaming PDFs not being that common (or so I believe). While not comfortable giving up my ID & password, there may be an alternative. I'll send a PM with an explanation. Thanks for the attention.

P.S. and I did try 1.9.7.9, but no success

Just thinking out loud since its not reproducible, could it be a corrupted setting or profile? Would a reset fix it possibly? Have you already tried with a clean profile to see if it persists? There was a recent update from Adobe for Acrobat, did the plugin get jammed up by any chance? Just thinking out loud to see if maybe something you haven't done that might fix the problem.

GµårÐïåñ wrote:Just thinking out loud since its not reproducible, could it be a corrupted setting or profile? Would a reset fix it possibly? Have you already tried with a clean profile to see if it persists? There was a recent update from Adobe for Acrobat, did the plugin get jammed up by any chance? Just thinking out loud to see if maybe something you haven't done that might fix the problem.

I appreciate the thought and welcome the options, but it's happened on 3 different machines with different levels of noscript from 1.967 (iirc) to latest beta installed. The 4th machine with v1.95 installed works fine. If we uncheck forbid other plugins in NS options, it also works. So I haven't tried a profile reset, but I don't think the data is pointing in that direction.

Thanks

Understood. Just to add, I wasn't suggesting that you dump or lose your profile, just maybe creating a new ones using the -profilemanager option on one of the problem machines and just install NoScript to see if it works or still no go. This will tell us ALOT because should it work, then it would point towards a corruption or possible conflicts rather than an NS problem. But if still no go, then it at least eliminate conflict and corruption and we can focus on the cause more specifically as Giorgio already has. If you could try that as a matter of good will, just to be sure, that would be great, otherwise, I will just let you guys figure it out. Good luck.

GµårÐïåñ wrote:Understood. Just to add, I wasn't suggesting that you dump or lose your profile, just maybe creating a new ones using the -profilemanager option on one of the problem machines and just install NoScript to see if it works or still no go. ...<snip>... If you could try that as a matter of good will, just to be sure, that would be great, otherwise, I will just let you guys figure it out. Good luck.

Just to be clear you're referring to the FF profile manager, right? I didn't find information on a NS profile but wanted to be sure.

Yes, the Firefox profile manager.

Yes, as Alan already responded, I mean the Firefox profile manager.

Just thought I would post a note and let you know that the problem I had with streaming PDFs seems to have been resolved sometime (I think) within the last couple of releases. We had tried several things behind the scenes via PM with little success so I had been using a workaround of unchecking forbid other plug-ins. I forgot to do that this week yet it still worked. Good News. Thanks for the help.

Glad to hear it worked out for you. Some regressions were addressed in the last few releases that may have addressed the issue. Thanks for letting us know it is working.

For anyone who has the issue, please update to the latest development build and report back if you still experience the same issues.