Bug 76979 - dpms failure after upgrading to 8.0
dpms failure after upgrading to 8.0
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver (Show other bugs)
8.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-30 10:15 EST by Need Real Name
Modified: 2012-11-02 11:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-10 15:29:17 EST
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 Need Real Name 2002-10-30 10:15:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
dpms fails to function even after selecting Standby, Suspend, and Off, even
though the entries are correctly recorded in .screesaver, and after
running xscreensaver-command -restart
The video driver is a generic s3 and the display is a ViewSonic VPA150.

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


How reproducible:
Always

Steps to Reproduce:
1.Redhat-> preferences -> screensaver -> advanced -> change settings
2.run xscreensaver-command -restart
3.nothing happens at the display
	

Actual Results:  Ok, this is getting repetitive.  It doesn't blank the screen or
go to energy-saving mode.

Expected Results:  Power-saving mode should be entered.

Additional info:
Comment 1 Bill Nottingham 2002-10-30 22:31:05 EST
Any errors in the X logs?
Comment 2 Bill Nottingham 2002-11-07 18:56:04 EST
Bug reporter says:

The answer is: no errors in the log file, just an audit comment at the foot
saying "Client 14 rejected from local host."
Comment 3 Ray Strode [halfline] 2004-11-10 15:29:17 EST
Hi,

This bug is quite old now.  Given the lack of activity on this report and the
likelihood that this bug has already been fixed, I am going to close it.  If you
encounter the problem discussed in this report with Fedora Core 3 or a recent
version of xscreensaver, feel free to reopen.

Thanks

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