Just updated to 2.3.2 yesterday and experienced the same problem. I never updated to 2.3.1, so I can't talk about that. Figuring it obviously must have something to do with the update, as I had...