Comment 2 for bug 184122

At this moment the reactivation of the display is working for me (suspending with Fn+F3 is not, though).

I'm not sure if it go fixed by one of the updates or by the fact that a few days ago I had to reinstall the nvidia proprietary drivers.
(It's been a couple of times already since a updated to Hardy that in one of the daily updates I get a "-386" linux image instead of a "-generic" one. When this happens after restarting the standard vesa driver gets loaded and I have a hard time changing back to nvidia - typically, I have to reinstall the drivers, but I'm not sure that's how I get it to work. This time around I got the nvidia driver back but I now don't get the nvidia splash screen that I used to get on X boot - not big deal, just weird behavior).

I'm not sure if the fact that I'm running hardy on a Thoshiba laptop justifies the difference in our experience.

I have an Inspiron 9400 (with intel graphics) running gutsy, but I'm not planing to upgrade to Hardy until it goes into Beta (or even GA, if I manage to wait that long).
When I do upgrade I'll report back here.