Bug 127318
Summary: | $LOCK_X nonfunctional in apmscript probably due to typo or changed fields in /usr/bin/w | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Glick <typrase> |
Component: | apmd | Assignee: | Zdenek Prikryl <zprikryl> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-07 14:32:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jesse Glick
2004-07-06 16:45:31 UTC
Another note about my last comment re. a hang after using the patch: I do use a wrapper script which invokes "xscreensaver-command -lock -display :0" before running "apm -s", and this works fine almost all of the time, without needing to set $LOCK_X in /etc/sysconfig/apmd. (About one time in ten after resuming, the xscreensaver unlock screen does not appear - I see the contents of my Gnome desktop but no X input events work - which can be worked around using "killall -HUP xscreensaver" from a virtual console.) But the code in apmscript (for Gnome) is significantly more complicated. |