I have a stock M1 MBP 8GB/256GB, with only default apps installed (I didn’t install any other apps), on the latest Big Sur.
Today, when I woke it up and it asked for my password, the strangest thing happened: I barely managed to put in the first character, when suddenly it “took over” and a string of characters appeared (the dots) one after the other like a train, without my inputting anything, and it took up the whole box, and I assume kept going. It felt exactly as if a key was stuck - but I nothing was pressed, and I looked very carefully over the keyboard and didn’t see anything stuck anywhere. Of course, when I hit “return”, it shook, indicating wrong password. I tried several times, and the same thing kept happening. So I restarted it from the power button, but when the screen presented itself, the same thing kept happening.
When the screen with the password box appeared again, it had the buttons for “shut down” and “restart” and I hit “shut down”, but it restarted instead. I did this several times and it kept re-starting as if I was pressing the “restart” dialogue. Strange.
Anyhow, I kept fooling around and somehow one time it allowed me to input the password normally, and I finally managed to get in.
Naturally, I searched online for the problem with DuckDuckGo, and in fact found the exact description of the problem I had, but when I clicked on the link, it discussed a different problem… so the link and the description didn’t match at all.
Regardless, I thought perhaps it’s a OS issue, so I decided to update to Monterey 12.1 (from Big Sur). When it asked me for my password to update the OS, again the problem occurred with the “stuck key” effect, but after a couple of tries, it allowed me to input my password normally.
So I updated to MacOS 12.1 and when the password box presented itself, I had no problem inputting my password normally.
I hope that’s the end of the problem, but in the link description I found with DuckDuckGo, the guy complaining about the problem said it doesn’t happen every time but happens frequently, so we’ll see if it carries over to 12.1.
Anyhow, anyone else see this bug? TIA!
Today, when I woke it up and it asked for my password, the strangest thing happened: I barely managed to put in the first character, when suddenly it “took over” and a string of characters appeared (the dots) one after the other like a train, without my inputting anything, and it took up the whole box, and I assume kept going. It felt exactly as if a key was stuck - but I nothing was pressed, and I looked very carefully over the keyboard and didn’t see anything stuck anywhere. Of course, when I hit “return”, it shook, indicating wrong password. I tried several times, and the same thing kept happening. So I restarted it from the power button, but when the screen presented itself, the same thing kept happening.
When the screen with the password box appeared again, it had the buttons for “shut down” and “restart” and I hit “shut down”, but it restarted instead. I did this several times and it kept re-starting as if I was pressing the “restart” dialogue. Strange.
Anyhow, I kept fooling around and somehow one time it allowed me to input the password normally, and I finally managed to get in.
Naturally, I searched online for the problem with DuckDuckGo, and in fact found the exact description of the problem I had, but when I clicked on the link, it discussed a different problem… so the link and the description didn’t match at all.
Regardless, I thought perhaps it’s a OS issue, so I decided to update to Monterey 12.1 (from Big Sur). When it asked me for my password to update the OS, again the problem occurred with the “stuck key” effect, but after a couple of tries, it allowed me to input my password normally.
So I updated to MacOS 12.1 and when the password box presented itself, I had no problem inputting my password normally.
I hope that’s the end of the problem, but in the link description I found with DuckDuckGo, the guy complaining about the problem said it doesn’t happen every time but happens frequently, so we’ll see if it carries over to 12.1.
Anyhow, anyone else see this bug? TIA!