can't suspend from keyboard + screen remains off

Suspend did work in Hardy Alpha5 until I installed the nvidia proprietary driver (Dell Inspiron 6400, Go7300). Now the display fails to reactivated as you describe.

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.

I also don't get the splash screen.
Just updated to nvidia-glx-new 169.12+2.6.24.10-12.30 but still no go reactivation. I would have thought that ctrl-alt-backspace would reinitialize the display, but that did not work either, nor ctrl-Alt-F1 to get a text console.

I might try doing a complete remove and reinstall.

Installed Hardy Alpha 6 yesterday.
Unlike Alpha5, was prompted to install nvidia driver, good.
However, even after the updates installed, suspend would still not work.

Dell Inspiron 6400 with Nvidia Go 7300

thanks for reporting! but since this bug has been reported during alpha and not been touched since i dare to ask if it still is a problem. if it still is, please file it against a specific package so the relevant people will have a look at it...

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.