[oe-issues] [Bug 2770] New: Wanted: Option to disable spitz keys which cause un-wanted power on

bugzilla-daemon at tinman.treke.net bugzilla-daemon at tinman.treke.net
Wed Aug 15 09:55:16 UTC 2007


http://bugs.openembedded.org/show_bug.cgi?id=2770

           Summary: Wanted: Option to disable spitz keys which cause un-
                    wanted power on
           Product: Openembedded
           Version: Angstrom
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Distributions
        AssignedTo: openembedded-issues at lists.openembedded.org
        ReportedBy: carbonfreeze at gmail.com


Currently, the spitz wakes on the following key-presses:

Tab/CapsLock
FN
Ctrl
Home
Address
Mail
Home

When the spitz is used as a portable device (example: carried in pocket or belt
clip) these key presses can cause the machine to turn on and waste power or
spam open applications with key presses. When the spitz is carried with the lid
closed and bumped, occasionally it will power on due to the Tab, FN or Calendar
buttons being pressed by the lid.

It would be nice to have an option to disable power-on by keyboard keys, or
have wake by keyboard keys disabled completely. Reasons for this include:

1). Increased battery life. Even if the device is only on until the sleep timer
turns the machine off, this decreases useful time of the device. In the case
where another key is being pressed by the lid, (Q key seems to be fairly
common) it causes the machine to be on for long periods of time.

2). Open documents or applications are spammed with key presses. I have had
issues with gpe-contacts creating, deleting or renaming contacts due to
keypress spam. Example: new contact created with "QQQQQQQQQQQQQQQQQQQQQQQQQQQQ"
in all fields; or current contacts have info changed. Also have had issues when
mrxvt or emacs is open.


-- 
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.




More information about the Openembedded-issues mailing list