[oe-issues] [Bug 2811] New: gpe-clock alarm resume disables keyboard when gpe-lock is used

[bugzilla-daemon at tinman.treke.net]

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

           Summary: gpe-clock alarm resume disables keyboard when gpe-lock
                    is used
           Product: Openembedded
           Version: Angstrom
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Distributions
        AssignedTo: openembedded-issues at lists.openembedded.org
        ReportedBy: carbonfreeze at gmail.com
        Depends on: 2219,2810
            Blocks: 2156


Normally when suspend/resume is used (power button) gpe is locked on resume and
user must re-enter passphrase to access gpe. When an alarm is scheduled via
gpe-clock and the machine wakes for the alarm, the passphrase prompt to unlock
gpe does not appear. This causes the keyboard to be un-usable. Doing a
suspend/resume cycle does not resolve the issue. Ctrl-Alt-Del can be called to
restart X, or the touchscreen can be used to log out of GPE.

Steps to reproduce:
1). Install angstrom-x11 on device. Update & Upgrade.
2). Install gpe-clock & at (gpe-clock depends on at for scheduling, see Bug
#2219)
3). mkdir /var/spool/at & chmod 777 /var/spool/at (to allow users to add events
to atd). See Bug #2810.
4). Start gpe-clock, create an event at least 5 minutes into the future and
suspend device.
5). Upon alarm event, atd will resume device and bypass gpe-lock.


Adding Bug #2219 & Bug #2810 as blockers to get various gpe-clock & atd issues
cleaned up. Blocking 2156 because I'm using that device.

Used Angstrom-x11-image-glibc-test-20070804-spitz-installkit.tgz as install
media on machine spitz (slc-3000), fresh ipkg update;ipkg upgrade performed as
of bug report.


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