Yup - it sure does. But I also have one user where the User Account works OK. This account was for testing purposes and I'm pretty sure it was created prior to upgrading Civi - I can't be sure.
I should also note here that I have an almost identical deployed installation that works fine with 3.1.beta5, so I believe this problem was introduced in 3.1.1. It's also not a deployment issue; the behavior is the same on both sandbox and production sites.
Perhaps there's something else that's breaking it in conjunction with Civi - all I can tell you is that when Civi is disabled, the "My Account" link (and corresponding User Account view) work fine. But when Civi is enabled, User account page requests are redirected to the front page, without an error. The only way I can verify that the view actually exists is to disable Civi, at which point everything is normal.
UPDATE: OK - there's no way to check on the Civi sandbox without superadmin access to the Drupal side - do you have additional users and can you access their accounts? On my site (which, until this problem was only a few days away from launch), I have one superadmin and two test users - one of the test users is accessible, the superadmin and other test user aren't.
The one thing that's consistent is this: disabling Civi once again allows access to the user account pages.
If you want to look into this on the deployed pre-launch site, I'm happy to furnish you with the required info to poke around. This is a pretty major issue and there are others who have encountered this - at least one has run into the same problem and disabled pretty much everything until he tracked it down to Civi.
See
http://drupal.org/node/629456. Any guidance really appreciated - this is now holding up launch of the site.
I'd say this is pretty serious and specific to 3.1.1 - Thanks much for any help!
(Possibly related: When I first go to Civi, I get an "You do not have permission to view this contact record. Contact the site administrator if you need assistance" message twice, which goes away once I reload the page.)