screen rotates to portrait sometimes

Cannot reproduce this

Scott Sweeny just repro'd this.

This sounds like a bug in the video driver. Probably should be escalated to nvidia, although they'll likely want a more defined set of steps to reproduce.

Agreed with comment #3, from past experience with nvidia we should have a clear and concise list to reproduce this before filing a bug with upstream. Along with any valuable logs/data

The fact that display gets rotated but not input makes me think it's some flaw in the tegra3 driver's RANDR handling on resume. If this were on an open source driver, I'd suggest switching on DRI debug flags so we could detect if RANDR events are getting triggered on suspend, however I don't know if tegra provides that debug data in any form. It does not look like there are xorg.conf debugging options that would help.

gnome-power-manager on the other hand does have log data available. If someone can turn that on, reproduce this issue and then collect and attach that log here, it might give some clues.

It would also be interesting to see whether this can be triggered just by ordinary suspend/resume cycles or if it depends on the battery level and/or cord plugging. The g-p-m log might answer that. Or perhaps manually suspend/resume (via pm-suspend I guess?) and experiment with the power cord until you find a reliable reproducer.

will try to reproduce and gather data

This problem has also been seen in Raring 13.04, Please see bug# 1088741 .

I was asked to post my experience with this bug (when I posted 1088741). Unfortunately, I haven't been able to reproduce it. It seemed to have something to do with moving (not removing, just moving) the power connector during the time when the system was coming up. It happened twice but I haven't been able to get it to happen again. Probably it's some type of hardware falt due to the slight power glitch as the system comes off external power and then back on again, but seems to only be an issue as it's starting up. (Definitely not as important of a problem as the "button1 stuck" problem!)