User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:220.127.116.11) Gecko/2008091816 Red Hat/3.0.2-3.el5 Firefox/3.0.2 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:18.104.22.168) Gecko/2008091816 Red Hat/3.0.2-3.el5 Firefox/3.0.2 We have a Juniper Networks SA-2000 appliance that we utilize to do webinars with. We uploaded a new cert from Verisign and when users login to conduct a webinar it goes to a blank page, which then they have to relog in (and then it lets them), and when they go to start a meeting but it won't let them. I checked Firefox 3.0.1 and 3.0.2 (on Windows and Linux) and they don't have that issue, then I checked 3.0.4 and it has this issue. Reproducible: Always Steps to Reproduce: 1.Log in to webinar box (which just goes to a blank white screen. 2.Relog in again which takes us to our meeting (webinar) page. 3.Try to start an instant meeting but it is grayed out. Actual Results: Nothing happens. That's the problem. :) Expected Results: Allowed us to start an instant meeting like it will in Firefox 3.0.1 and 3.0.2 (what we tested). I am making the severity Normal, but the issue is widespread throughout our company so users will have to use Internet Explorer until this is addressed.
We recently updated several Mac OS X (10.5) boxes and Linux (Fedora and Red Hat) boxes to Firefox 3.0.4 and they do not experience the issue. This only seems to be happening with the 3.0.4 version for Windows. I also specified that our users are running Windows XP SP2 (some are now on SP3) but that doesn't seem to make a difference. I have been unable to verify this is an issue on Vista. Thanks.
Paul, do you still see this with newer version of firefox?
Whiteboard: [closeme 2010-07-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.11 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.