Closed Bug 394807 Opened 18 years ago Closed 15 years ago

I received this error message when I was logging in.

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: ladyjenavi, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-06-30])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 I am a new user and this is the first time I've logged in since the initial setup. It went straight to this page when I clicked on the login button. Reproducible: Always Steps to Reproduce: 1.log in from the bookmark for the bug report I submitted. 2. 3. Actual Results: seem to always get this message. Assume that I can't bookmark a bug report? Expected Results: log in and get to the page I bookmarked. The page says to send this to bugzilla-admin@mozilla.org with details of what I was doing at the time. I got into the bug report fine another way though.
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 2010-06-30]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x 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
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.