Bug 193193 - xscreensaver-command -time does not work
xscreensaver-command -time does not work
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xscreensaver (Show other bugs)
4.0
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Ray Strode [halfline]
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-25 19:08 EDT by Daniel Cotey
Modified: 2012-06-20 12:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 12:13:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel Cotey 2006-05-25 19:08:28 EDT
Description of problem:
xscreensaver-command -time should return the time since the last
activation/deactivation of the screen saver, instead it errors with a bad status
message.  This impacts people who use SGE/N1GE for cyclestealing, and probe for
user activity via the screensaver.

Version-Release number of selected component (if applicable):
xscreensaver-4.18-5.rhel4.10

How reproducible:
Always

Steps to Reproduce:
1. run xscreensaver-command -time
2.
3.
  
Actual results:
XScreenSaver 4.18
bad status format on root window.

Expected results:
XScreenSaver 4.10: screen non-blanked since Thu May 25 15:39:42 2006

Additional info:
It appears that the error condition (type != XA_INTEGER || nitems < 3) is always
being matched, possibly a 64bit int snuck in somewhere?
Comment 1 Jiri Pallich 2012-06-20 12:13:26 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.