There is one troubleshooting step that OS X shares with the classic Mac OS, removing preference files. But on OS X there are TWO folders:
/Library/Preferences and ~/Library/Preferences
--The latter being in your user/home folder--
Since the issue doesn't exist under another logon it is specific to that user folder. SO there is something specific to that user that is causing the problem. This takes the /Library/Preferences folder out of consideration for troubleshooting preferences. The first thing I would do is use a utility like Onyx to verify and clean the system. This includes verifying preferences files. After that rename the ~/Library/Preferences folder to something like
~/Library/Preferences-old
You'll probably have to do that in Terminal and use sudo as those files are owned by another user on the system. then create a new ~/Library/Preferences folder and reboot.
If you can now log into that account it is a simple (HAH!) matter of putting preferences files in the new Preferences folder and rebooting till you find which one it is.
No guarantee, though, that it is a preference file, it could be a startup item. So do the same thing with the ~/Library/LaunchAgents folder.
The other thing to consider is that it might be easier to just create a new user folder. Copy the things you need out of the old user folder and delete the old user. That could save you a lot of troubleshooting time. It would be my preferred way of doing it (after running Onyx) as I care less about what happened than just finding a fix that gets me up and running more quickly.
First, setting up separate admin and standard accounts was NOT a mistake. It is, in fact, a Good Idea™.
When you need to authenticate (for example, to unlock a padlock), you need to enter both your admin name and your admin password. If you're in your admin account, the name will be filled in for you. If you're in your standard account, both the name and password fields will be blank, and you need to enter them both. Be sure to enter the admin's name and the admin's password.
Best Answer
Do you have auto-login enabled for this user? If so you can probably reboot and get back in.
If you see the 'Other' user at the Login Window you can use that, too.
If all else fails you try ssh'ing in from another system (
ssh user@computer.local
) or booting up in single user mode (Command-S
on startup).