It sounds like a small glitch in your Mountain Lion upgrade. If you're just done an in-place upgrade (not a clean install) these things can happen.
It sounds like you've found the workaround. But if you discover other problems with the upgrade, you should consider a clean install. Do a Google search on "clean install Mountain Lion" to find out how.