#9780 NORM Not Tri: os49 - suspend does not recognize user's external device activity
Zarro Boogs per Child
bugtracker at laptop.org
Tue Dec 1 19:37:40 EST 2009
#9780: os49 - suspend does not recognize user's external device activity
------------------------------------+---------------------------------------
Reporter: mikus | Owner:
Type: defect | Status: closed
Priority: normal | Milestone: Not Triaged
Component: not assigned | Version: Development build as of this date
Resolution: wontfix | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
------------------------------------+---------------------------------------
Comment(by mikus):
Replying to [comment:1 cjb]:
> > Not paying attention to the external USB keyboard is a regression from
"how to avoid suspend" on the XO-1.
>
> I think you're misremembering, Mikus. The USB controller has never been
powered during suspend, on any XO.
[[BR]]CJB and Quozl -- you are talking about the status *after* suspend
happens -- what I am talking about is the status *before* suspend happens.
Here is how I operate on 802: I normally have /etc/ohm/inhibit-idle-
suspend defined. But sometimes I don't - the question then is: "how do
__I__ prevent 'suspend' ?" when it would happen if I did nothing. What I
do, upon noticing that the screen has dimmed, is to press <shift> upon my
external keyboard. [Note: since 'suspend' has not yet happened, the USB
keyboard is still powered up at this time.] My keyboard-press tells the
system "user activity is taking place" -- and the system resets its
countdown_to_suspend (and "undims" the screen).
The same procedure (for __me__ to avoid soon-to-happen suspend) works for
me on XO-1 builds since 803 (whether Joyride, or SoaS, or F11-on-XO1).
--
Ticket URL: <http://dev.laptop.org/ticket/9780#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list