Comment 5 for bug 144305

Okay, I'm sure your workaround is the way to go, it's just the implementation which doesn't seem to be the same between my computer and yours.

Notes:

If I manually switch to vt1 and sleep using "/usr/lib/hal/hal-system-power-pmu sleep", it sleeps and resumes fine.

Also, if I sleep from X by running "pbbcmd sleep", it runs /etc/power/suspend.d/console-switch-out and sleeps and resumes okay, but for some reason /etc/power/resume.d/console-switch-in is not being run and so after wakeup I have to switch back to vt7 by hand.

But if I try and sleep just by closing the lid, I get the backlight switching on after it goes to sleep, and the machine dies on resume.

Am I correct in thinking that the /etc/power scripts are called from userspace by pbbuttonsd or pmud? So if the PMU ioctl is being called by some other process, those scripts will not necessarily be run?

I think it's gnome-power-manager which is handling the lid-close event, and not running the scripts. So I just need to find out where to hook into there to do the vt switch. I suspect it's happening in /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux; if that's the case it should be a piece of cake to fix.