Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 62161 - apmscript/apmcontinue fail to run on restore
Summary: apmscript/apmcontinue fail to run on restore
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks: 61901 67218 79579 CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2002-03-28 01:33 UTC by Chris Runge
Modified: 2008-08-01 16:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:39:28 UTC
Embargoed:

Attachments (Terms of Use)

Description Chris Runge 2002-03-28 01:33:23 UTC 
Description of Problem:

Hampton beta 3 (aka Skipjack)

on my Dell Latitude CPx I created an apmcontinue script under
/etc/sysconfig/apm-scripts that would reset the keyboard rate. After some
testing, however, it appears that neither apmscript nor apmcontinue are executed
after awakening from a suspend initiated by apm -s

Version-Release number of selected component (if applicable):

apmd-3.0.2-7

How Reproducible:

every time

Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:
Comment 1 Bernhard Rosenkraenzer 2002-04-12 16:34:59 UTC 
apmd seems to do the right thing... Possibly the kernel not sending the correct events to  
userspace under some circumstances?
Comment 2 Arjan van de Ven 2002-04-14 13:40:19 UTC 
I really doubt that.... after all if that were the case nobody would have
networking after resume since we disable network just before suspend via similar
mechanisms
Comment 3 Bugzilla owner 2004-09-30 15:39:28 UTC 
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/
Note You need to log in before you can comment on or make changes to this bug.