Closed Bug 56664 Opened 24 years ago Closed 24 years ago

Cannot log in to Bugzilla

Categories

(Core :: DOM: Core & HTML, defect, P3)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: stephe, Assigned: rods)

References

(
URL
)

Details

When I try to log in to Bugzilla using Mozilla, I get the error:

"The e-mail address you entered (stephe@wenet.net) didn't match our minimal
syntax checking for a legal email address. A legal address must contain exactly
one '@', and at least one '.' after the @, and may not contain any commas or
spaces."

My email address in the URL looks like "Bugzilla_login=stephe%40wenet%A9net".

If I use NN4 to log in, it works ok, and my email address in the URL looks like
"Bugzilla_login=stephe%40wenet.net".  I would have to say that the %A9 that
Mozilla uses is wrong.

To reproduce, log out of Bugzilla and try to enter a new bug.

Tested with Mozilla 101406 on Linux.
WFM 2000101409 linux
works for me too, linux 2000101015 - marking invalid
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
reaper: if it works for you, you mark it WORKSFORME, not INVALID.

This has actually been seen by several people, although nobody can work out why.
I am reopening this bug since it is still happening to me with Mozilla 101506 on
Linux.  I am not making this stuff up, and I think it is an abuse of Bugzilla to
so carelessly mark a bug INVALID.  I could not even to use Mozilla to comment on
this bug since I cannot log in.  I had to resort to NN4.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
hmm ... my bad, I thought this was related to the the faulty builds the other
day that didn't allow ANYONE to log into bugzilla. That's why I marked it
INVALID - lesson learned for me .... still, a lot of people are not seeing this
bug, so if you're around on tuesday, let's meet on #mozillazine, grab some linux
folks, and see if we can make this one go away ....


Sigh.  Now I find that this is an invalid bug after all.  It turns out the
problem was my character coding was set to Armenian which is strange since I
never set that myself.  What is even stranger is that Mozilla would keep
switching back to Armenian no matter how many times I chose Western and my
default character code in Preferences is Western.

In any case, I created a new profile, and the problem went away.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → INVALID
verifying as for reporter's coments
Status: RESOLVED → VERIFIED
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.