Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Diazruanova on September 16, 2010, 04:45:42 PM
-
HI,
Today, after updating FireFox from 3.6.9 to 3.6.10 I was NOT able to open it when Sandboxed with an XULRunner error: see attached JPG.
In fact, I tried to open a Sandboxed "Safe mode"of this new version, but to no avail, so here any add- on can be ruled-out of the equation.
When running UN-Sandboxed, this new FFx version runs perfectly fine, either in "Safe Mode" or in the Standard one.
Thanks
-
I had a similar problem running previously Firefox in the sandbox. Whenever there was an update to a plug-in, or Firefox itself, upon restart/new start it would go in circles not allowing me to carry out any modifications to it(same updates over and over). Also any downloaded programs would not install completely if launched from download manager in Firefox. The best way to get around the updates problem was to take Firefox out of the sandbox emulation, and do everything then. Afterwards everything in sandbox emulation was updated and running as expected. Also installing directly through windows explorer was the only option for downloaded programs.
-
Did you have the same error window as I do?
I had a similar problem running previously Firefox in the sandbox. Whenever there was an update to a plug-in, or Firefox itself, upon restart/new start it would go in circles not allowing me to carry out any modifications to it(same updates over and over). Also any downloaded programs would not install completely if launched from download manager in Firefox. The best way to get around the updates problem was to take Firefox out of the sandbox emulation, and do everything then. Afterwards everything in sandbox emulation was updated and running as expected. Also installing directly through windows explorer was the only option for downloaded programs.
-
have you updated FF inside or outside of sandbox? thanks
-
No. In my case that didn't happen. It was however two months or so ago.
Did you have the same error window as I do?
I had a similar problem running previously Firefox in the sandbox. Whenever there was an update to a plug-in, or Firefox itself, upon restart/new start it would go in circles not allowing me to carry out any modifications to it(same updates over and over). Also any downloaded programs would not install completely if launched from download manager in Firefox. The best way to get around the updates problem was to take Firefox out of the sandbox emulation, and do everything then. Afterwards everything in sandbox emulation was updated and running as expected. Also installing directly through windows explorer was the only option for downloaded programs.
-
have you updated FF inside or outside of sandbox? thanks
At first, I forgot totally that it was Sandboxed, and I proceeded to update it and then the error appeared, so I downlaoaded the whole installer and updated it UN-sandboxed. FireFox updated fine, but now it does NOT open while sandboxed showing the error window, otherwise it runs fine.
-
Diazruanova,
I noticed that in your Signature you are using an older version of Avast. Perhaps if you update to the newest version of 5.0.677 this may help. Reboot after upgrading. Thanks.
-
I have had the same problem this morning when updating Firefox. Same error as originally reported. I repeated the update OUT of Sandbox mode and that worked OK and so does FF but only OUT of Sandbox mode, still fails in Sandbox mode. I have 5.0.677 Avast Internet Security package running.
-
It appears that most of you have updated FF to v.3.6.10 outside of the SB and got this error/problem using AIS 5.0.677.
I am going to need the assistance of the Avast Team for trouble-shooting on this. Please bear with me.
Edit: An Avast Team member was notified, so we need to wait for a solution. Thank you for your patience.
-
Hi all,
@SafeSurf thank you for the message alerting me to this.
I will try to find out exactly what is happening here and ask our QA guys to recreate the scenario and do some testing to determine what is causing this. I will post back here as soon as I can.
Many thanks,
Adam
-
I will try to find out exactly what is happening here and ask our QA guys to recreate the scenario and do some testing to determine what is causing this. I will post back here as soon as I can.
Thank you Adam. And thank you to our Avast users for your patience. :)
-
Hi guys,
As promised, a small update on the situation. The QA guys have managed to recreate the situation here at avast HQ and are therefore currently working on how to get this solved. I will get more news to you as soon as we have it.
Also as per SafeSurf's message, thank you for your patience :)
Best,
Adam
-
Thank you very much for your response!!! ;)
-
Hi, any further news on this one? Since only a few people have indicated an interest in the topic does that mean this problem is only affecting a very few users?
It might be nice if there was a poll button on each topic which meant "yes, I'm interested and also waiting for a solution" so that users could express interest without necessarily having to enter a reply. Would that help the Avast staff prioritise? If not, how do they prioritise currently?
-
Well, since avast has been able to re-create and acknowledge the problem, it would be nice for them to reply with the info on how and when this issue is going to be solved, IMO
-
For now I have disabled the sandbox waiting for a resolution to this issue.
Martin.-
-
As promised, a small update on the situation. The QA guys have managed to recreate the situation here at avast HQ and are therefore currently working on how to get this solved. I will get more news to you as soon as we have it.
Also as per SafeSurf's message, thank you for your patience :)
Best,
Adam
The Avast Lab first needed to replicate the problem, then find the solution to fix it; they do not work on the weekend. This all occurred after FF upgraded to 3.6.10. So Avast is aware of it and are trying to fix it as soon as possible. Thank you again for your understanding.
-
Oh, OK thanks again and please keep us posted as soon as there are news :-)
-
The Avast Team will reply to all of you in this thread.
-
Glad to see the avast! team is working on this.
However, just a FYI for those who have not done the 3.6.10 update; the only item the 3.6.10 upgrade was issued for:
Fixed a single stability issue affecting a limited number of users.
http://www.mozilla.com/en-US/firefox/3.6.10/releasenotes/
Unless you're are one of the "limited" users being affected by the stability issue really no pertinent (i.e., security/vulnerability) reason to install the update. Hence, I have no intention of installing 3.6.10 on any of my three systems; i.e., why fix it if it's not broken. ;)
FYI -- Security Advisories for Fx 3.6.X:
http://www.mozilla.org/security/known-vulnerabilities/firefox36.html
-
Good point Jon_T, maybe a reason to think about turning off auto-updates. Sometimes it rains on even the well-meaning and (self-)righteous!!
-
Good point Jon_T, maybe a reason to think about turning off auto-updates. ...
I learned a long time ago to disable auto updates for all my apps.
When a update is released I wait for 3-5 days and read the forums to see if users are experiencing any problems/issues from the update. Over the years this has saved me from quite a few of problems/issues resulting from updates. ;)
-
Hi,
Kind of curious about how long it would take to create a work-around on this problem and have FFx 3.6.10 running again Sandboxed: ...it took no more than 8 minutes and now it is running fine and opening without problems SANDBOXED!
1.- Downloaded a fresh copy of FireFox 3.6.10 from Mozilla´s site
2.- Backed up my profile with MozBackup
3.- From the Add-Remove programs control panel, I Uninstalled FireFox deleting everything related to it (the uninstaller has this option)
4.- From the Add-Remove control panel I repaired avast´s installation
5.- Proceeded to install the fresh Firefox new version
6.- Re-boot the PC
7.- Right-click on Firefox´s icon and click on the "Always Run in SandBox" option
8.- Restored with MozBackup the original previously backed-up copy of my FFx profile
9.- Launched FireFox 3.6.10 ...and voila! FFx again is running SandBoxed
Total time from number 1 to number 9: 7 minutes and 30 seconds aprox
This does NOT mean that you guys from avast are exempt of the responsibility of fixing this bug ehhh??? ;)
-
@ Diazruanova,
It looks like you discovered a good work-around that perhaps others should take a look at. Maybe someone should hire you. ;)
-
@ Diazruanova,
...Maybe someone should hire you. ;)
Yes, that would be nice, maybe avast? what do you think? :)
-
Yes, that would be nice, maybe avast? what do you think? :)
;)
-
Hi,
Kind of curious about how long it would take to create a work-around on this problem and have FFx 3.6.10 running again Sandboxed: ...it took no more than 8 minutes and now it is running fine and opening without problems SANDBOXED!
I think I can beat your 7.5 mins and get it down to about 2 mins (standing on the shoulders of giants of course)! All I did was to download Mozbackup (since I wasn't aware of it before), install and run a backup and hey presto after that FF3.6.10 comes up and runs in the Sandbox as easy as you like...... unless of course someone did something else sneaky behind the scenes in FF or Avast and didn't let on? Bit of a coincidence though if so.
As said by Diazruanova, it would nice to have an official fix - or maybe all we need now is an explanation?
-
...... unless of course someone did something else sneaky behind the scenes in FF or Avast and didn't let on? Bit of a coincidence though if so.
Well, probably they did something behind the scenes with avast, because MozBackup exclusively backs up the Firefox´s profile and does not modify FireFox at all.
-
MozBackup
Very good tool!
-
Well, probably they did something behind the scenes with avast, because MozBackup exclusively backs up the Firefox´s profile and does not modify FireFox at all.
Surely that's not possible (they said they would tell us!) - anyway how could any such change happen with only database updates?
I ran FF out of the Sandbox - as I've had to become accustomed to for over a week, downloaded MozBackup, ran a backup, closed FF, went to eat, 30 mins later started FF in the Sandbox - magic! I just love coincidences... and believe in conspiracy theories, and fairies and ....
Come on Avast - someone must know what's going on by now. 10 days ago, or whenever this topic started, I was about to tell everyone how great the service was - glad I held off a while. An update, any update would be good, pleeeeease.
-
Come on Avast - someone must know what's going on by now. 10 days ago, or whenever this topic started, I was about to tell everyone how great the service was - glad I held off a while. An update, any update would be good, pleeeeease.
don't worry, I keep an eye on this thread...
it's a conflict between normal and sandboxed FF environments (something like this: http://forum.avast.com/index.php?topic=63033.msg538116#msg538116) - I'll need to simulate this in my lab,
-
don't worry, I keep an eye on this thread...
it's a conflict between normal and sandboxed FF environments (something like this: http://forum.avast.com/index.php?topic=63033.msg538116#msg538116) - I'll need to simulate this in my lab,
Thanks Pk and please do not forget that you owe me some info on this topic:
http://forum.avast.com/index.php?topic=63613.msg539119#msg539119 ;)
-
If it's any consolation, Firefox 3.6.10 broke a number of things, not just in Avast!. I regularly use a site that is powered by Wikia, and could no longer log into that site after the update (other than as guest). I ended up uninstalling 3.6.10 and reinstalling 3.6.8 and my login works again. I don't care what their release notes say, they changed more than they are admitting to!
-
If it's any consolation, Firefox 3.6.10 broke a number of things, not just in Avast!. I regularly use a site that is powered by Wikia, and could no longer log into that site after the update (other than as guest). I ended up uninstalling 3.6.10 and reinstalling 3.6.8 and my login works again. I don't care what their release notes say, they changed more than they are admitting to!
Too bad you did not download and install Fx 3.6.9 since it includes fixes for ten (10) critical Security Vulnerabilities (http://www.mozilla.org/security/known-vulnerabilities/firefox36.html) in 3.6.8.
Though the problem occurred after the 3.6.10 update problem may not have been solely to Fx version 3.6.10. Not too uncommon for various things to happen with all the files within the Profile's folder, and sub-folders.
I never use the internal Fx updater. Always download new version, shutdown Fx, backup Profile folders, then install the update. That if something awry after the update, it is easy to return back to the previous version.