Derek Broughton wrote:
> From: "Stefan Bellon" <sbellon@...>
> > Ah, I'm not so sure about that. The tests when acpid was not
> > running didn't put the notebook in S1 obviously. And therefore it's
> > clear that when opening the lid again, the second lid event occurs.
> > But when acpid is running, the notebook goes to S1 when the first
> > lid event occurs. When you open the lid again, the second event
> > /should/ occur, but the notebook is sleeping. Then you press the
> > power button and /that/ event is recognised. Perhaps the lid
> > opening is then "remembered" and inserted into the event queue.
> Nothing you did _should_ have put the notebook in S1. acpid had to
> have done that.
Sorry, that's what I meant with "when acpid is running ...". Yes, when
acpid is running and has the lid button script recognised, /then/ acpid
puts the notebook into S1 if the lid is closed. That's what I meant to
> So I still say acpid is processing things in the wrong order.
But how should acpid get the lid event before the power button event?
> However, it seems we both may be making an invalid assumption - that
> is, you simply can't ever recognize any button push except the power
> button when you are in S1. That's a real bitch...
Yes, exactly. Either every event that occurred during S1 mode has to be
ignored when waking up, or they should be raised in the correct order.
Stefan Bellon * <mailto:sbellon@...> * <http://www.sbellon.de/>
PGP 2 and OpenPGP keys available from my home page
If the answer is Microsoft, the question must have been quite stupid.