Hello,
Please excuse me banging on about this, but it seems to me that for laptop
users this issue is pretty fundamental.
The last time I reported this I blamed it on poor old apmd or kcmlaptop.
However I now beleive this is incorrect.
After running a few tests here are the results:
Running from command prompt only:
Suspend by closing laptop lid - correct behaviour
Suspend by pressing 'Suspend' button - correct behaviour
Standby caused by BIOS timeout - correct behaviour
Suspend to disk from BIOS caused by BIOS timeout - correct behaviour
Runing X :
Suspend by closing laptop lid - Screen backlight goes out, on
opening lid causes
light to go on, but
system (not just X)
has locked solid.
Suspend by pressing 'Suspend' button - Laptop goes to sleep,on
opening lid laptop
appears to come on,
but system (not just
X) has in fact locked
solid.
Standby caused by BIOS timeout - correct behaviour !
Suspend to disk from BIOS caused - system (not just X) locks solid.
by BIOS timeout Thick blue vertical stripes now
cover the display.
So it seems to me that the real culprit is X !!! Short of dropping out of X
every time I leave my PC I am at a loss about how to correct this. Is there
some fundamental setting I have overlooked in the X setup ?
This happens on X 4.01 and 3.3.6-14mdk (and many earlier versions too). I have
a Dell Inspiron 7000 with an 8Mb ATI Rage Mobility Pro chipset.
Ever hopefull
Owen
