Gmail notifier will not log in




8 years ago
8 years ago


(Reporter: strobotron, Unassigned)


Firefox Tracking Flags

(Not tracked)




8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/533.18.1 (KHTML, like Gecko) Version/5.0.2 Safari/533.18.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: Gecko/20101026 Firefox/3.6.12 combined with Gmail notifier

Gmail notifier continues to show 'failed to log in' with certain e-mail addresses ... passwords have been checked and certain accounts are unable to log in.

Reproducible: Always

Steps to Reproduce:
1.Open Mozilla Firefox ... extension is set to auto-log in ... does not happen
2.Double click extension icon to bring up log-in window, enter e-mail address / password ... hit log in
Actual Results:  
Returns 'failed to log in' message.

Expected Results:  
log into gmail notifier

I have checked this with 3 different gmail accounts, I am able to log in with 1 account - but the other 2 do not work.

Comment 1

8 years ago
From -> If you can't login, please get 0.6.4 at or get it from the Add-ons sandbox until it is approved.

If you still have issues please contact the extension developer as this is likely an extension issue not a bug in Firefox

Comment 2

8 years ago
update: will now not log in for any of the 3 e-mail addresses i've tried.  running version of the notifier which is the current version available.
Summary: Gmail notifier will not log in for certain e-mail addresses → Gmail notifier will not log in

Comment 3

8 years ago
Reporter -> Are you still experiencing this issue?

Comment 4

8 years ago
Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site ->
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE

Comment 5

8 years ago
Unfortunately yes, still experiencing the problem ... though I imagine once FF gets the upgrade to 4.0 this will be a non issue
You need to log in before you can comment on or make changes to this bug.