Comment 2 for bug 109446

On 4/29/07, Paul Sladen <email address hidden> wrote:
> This bug is hard to process because it's a policy issue (a question)
> that needs to be decided:
>
> * Should USB insertion or Mouse movement cause wake-up on a
> suspended/hibernated system?

Yes.

> If there are other ways of resuming the laptop (eg. opening the lid,
> pressing the power or Fn button), then this issue really a bug, but a
> need to answer the above question.

The use case I am describing is a suspend that is triggered by
initiating suspend from the System --> Suspend menu. The lid of
the laptop isn't closed in this instance. However, if I suspend and
then close the lid and reopen it, the machine does resume.
Obviously, this is suboptimal.

> End of Policy issue, my own views:
>
> Personally (this is my own view and may not be correct), is that USB
> wakeup by default would be a bad idea (a faulty USB device, or one that
> resets itself, or a USB device that is unplugged and replugged at the
> power-source would cause wakeup).

I suspect that issues from faulty devices can all be resolved.
In fact, this is a non-issue, because David Brownell has already
submitted patches that cause USB to "just work" with wake-from-suspend.

> Mouse/keyboard, I'm not so sure about. Many people have 'cats'.

Wake-from-suspend as a result of keyboard and mousepad events
is the default behavior for Windows XP. It is the expected behavior for
standard users. We should provide the same, imho.