The tedious failure of Macs with M1 that are beginning to be reported — 2022
Macs with the M1 chip have revolutionized the world of Apple computers thanks to their performance and power. Until now, everything was good words and excellent compliments towards these first Apple laptops with their own chip, however, some users have begun to report problems with the change of users and the screen saver. In this post we tell you what these newmac crashesand what is the possible solution.
Big Sur User Switch Issues
The new macOS Big Sur operating system allows you to enjoy fast switching between users on the same Mac without having to first log out of one and then log in to a different user. This makes switching between different users much easier and more comfortable, but it is precisely this function that is causing problems in some Macs that mount the famous Apple M1 chip.
The problem is that when some users make use of this feature to be able to switch between different accounts quickly, the Mac automatically launches the screensaver. Also, if this were only the problem, the news would not be too serious either, but when the screensaver appears, the mouse follows the upper part and even if you try to move it, nothing else works.
Solution to this problem
In order to continue using the device, users are forced to do one of the following:
- Close and reopen the lid of the MacBook Air or MacBook Pro.
- Press the power button or TouchID.
- Use the letter combination Alt-Command-Q to return to the login page.
It is worth mentioning that the problem is happening in different models of Mac with M1 chip, that is, both in MacBook Air, MacBook Pro and Mac mini and indistinctly the version of Big Sur in which the device is found according to the MacRumors forums, forums from the Apple community and Reddit.
Another way to prevent this error from happening
If you do not want to have to go through the solution that we mentioned above, what we recommend until Apple corrects the fault is that turn off fast switching between users. Of course, you can also contact Apple so that they can suggest a solution to this problem and even guide you to carry it out. However it seems that this will be a persistent bug, at least until the nextmacOS Big Sur update.