Weird one... (couldn't unlock from sleep)

I enter my password and it tells me wrong name or password.
Ted Lee wrote on :
I hate it when there are irreproducible faults, although in this case I guess it's better than a permanent serious one. I went to wake up my Powerbook G4 (running 10.4.something), which I have set to require a password to wake from sleep. I enter my password and it tells me wrong name or password. OK, must have mistyped (that first character getting lost sometimes thing maybe.) Didn't work. Tried a couple of more times, typing very slowly. No joy. Eventually got the "failed too many times" error. OK, I have a couple of other accounts on the machine, so I told it to switch users and tried a different one. Same problem -- wouldn't take the password and eventually got the "too many times" error. Wondering how I'm going to recover from this (envisioning I'm going to have to find my master password) I shut it down by pressing and holding the power switch -- at least that worked! Restarted and everything's fine. Go figure.
Jolly Roger replied on :

In article fvf8vg$kdj$1@redacted.invalid, "Ted Lee" TMPLee@redacted.invalid wrote:

I hate it when there are irreproducible faults, although in this case I guess it's better than a permanent serious one. I went to wake up my Powerbook G4 (running 10.4.something), which I have set to require a password to wake from sleep. I enter my password and it tells me wrong name or password. OK, must have mistyped (that first character getting lost sometimes thing maybe.) Didn't work. Tried a couple of more times, typing very slowly. No joy. Eventually got the "failed too many times" error. OK, I have a couple of other accounts on the machine, so I told it to switch users and tried a different one. Same problem -- wouldn't take the password and eventually got the "too many times" error. Wondering how I'm going to recover from this (envisioning I'm going to have to find my master password) I shut it down by pressing and holding the power switch -- at least that worked! Restarted and everything's fine. Go figure.

There were likely errors logged to the system and console log during those failed attempts. Those errors may help you determine what was going on.

Ted Lee replied on :

"Jolly Roger" jollyroger@redacted.invalid wrote in message news:jollyroger-549622.13443402052008@redacted.invalid

In article fvf8vg$kdj$1@redacted.invalid, "Ted Lee" TMPLee@redacted.invalid wrote:

I hate it when there are irreproducible faults, although in this case I guess it's better than a permanent serious one. I went to wake up my Powerbook G4 (running 10.4.something), which I have set to require a password to wake from sleep. I enter my password and it tells me wrong name or password. OK, must have mistyped (that first character getting lost sometimes thing maybe.) Didn't work. Tried a couple of more times, typing very slowly. No joy. Eventually got the "failed too many times" error. OK, I have a couple of other accounts on the machine, so I told it to switch users and tried a different one. Same problem -- wouldn't take the password and eventually got the "too many times" error. Wondering how I'm going to recover from this (envisioning I'm going to have to find my master password) I shut it down by pressing and holding the power switch -- at least that worked! Restarted and everything's fine. Go figure.

There were likely errors logged to the system and console log during those failed attempts. Those errors may help you determine what was going on.

Oh, I know that -- just too lazy to bother at the time.

Jolly Roger replied on :

In article fvg0do$546$1@redacted.invalid, "Ted Lee" TMPLee@redacted.invalid wrote:

"Jolly Roger" jollyroger@redacted.invalid wrote in message news:jollyroger-549622.13443402052008@redacted.invalid

In article fvf8vg$kdj$1@redacted.invalid, "Ted Lee" TMPLee@redacted.invalid wrote:

I hate it when there are irreproducible faults, although in this case I guess it's better than a permanent serious one. I went to wake up my Powerbook G4 (running 10.4.something), which I have set to require a password to wake from sleep. I enter my password and it tells me wrong name or password. OK, must have mistyped (that first character getting lost sometimes thing maybe.) Didn't work. Tried a couple of more times, typing very slowly. No joy. Eventually got the "failed too many times" error. OK, I have a couple of other accounts on the machine, so I told it to switch users and tried a different one. Same problem -- wouldn't take the password and eventually got the "too many times" error. Wondering how I'm going to recover from this (envisioning I'm going to have to find my master password) I shut it down by pressing and holding the power switch -- at least that worked! Restarted and everything's fine. Go figure.

There were likely errors logged to the system and console log during those failed attempts. Those errors may help you determine what was going on.

Oh, I know that -- just too lazy to bother at the time.

Oh, ok... then you'll excuse the rest of us if we don't bother wasting time helping you with this one. I mean, if you're too lazy to help yourself... ; )

Sander Tekelenburg replied on :

In article fvf8vg$kdj$1@redacted.invalid, "Ted Lee" TMPLee@redacted.invalid wrote:

[...] I enter my password and it tells me wrong name or password. OK, must have mistyped (that first character getting lost sometimes thing maybe.) Didn't work. Tried a couple of more times, typing very slowly. No joy. Eventually got the "failed too many times" error. OK, I have a couple of other accounts on the machine, so I told it to switch users and tried a different one. Same problem

Sounds like you accidentally changed to another keyboard input method and were in fact typing different characters than you intended -- which you wouldn't see in a passphrase field...

If you enable the "Show Input menu in Login Window" option (Sys Prefs->Accounts->Login Options) you will be able to solve this problem when it occurs.

However:

Restarted and everything's fine.

I wouldn't have thought a reboot would reset the input method. So maybe the problem was something else after all...