Bug 524360 - Xserver wakes itself up shortly after being put to sleep with "xset dpms force off"
Summary: Xserver wakes itself up shortly after being put to sleep with "xset dpms forc...
Keywords:
Status: CLOSED DUPLICATE of bug 582532
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: card_R300
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-19 12:25 UTC by Chris Rankin
Modified: 2018-04-11 14:54 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-30 14:29:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Log file for X server (106.88 KB, text/plain)
2009-09-19 12:25 UTC, Chris Rankin
no flags Details
dmesg log (36.23 KB, text/plain)
2009-11-26 22:16 UTC, Chris Rankin
no flags Details
xorg configuration file (3.82 KB, text/plain)
2009-11-26 22:16 UTC, Chris Rankin
no flags Details
X server log file (68.94 KB, text/plain)
2009-11-26 22:17 UTC, Chris Rankin
no flags Details

Description Chris Rankin 2009-09-19 12:25:58 UTC
Created attachment 361758 [details]
Log file for X server

Description of problem:
Whenever I try to force my monitor into "DPMS off" mode via "xset dpms force off", it typically wakes itself up again a few seconds later.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.6.3-4
xorg-x11-server-Xorg-1.6.4-0.1
and earlier.

How reproducible:
Very, although not 100%. Enough to be very, very annoying though. It typically takes 3-5 attempts before the "DPMS off" 'takes', but it has taken longer.

Steps to Reproduce:
1. xset dpms force off
2. Wait for it...
3. Ping! The monitor comes back to life!
  
Actual results:
I end up playing "whack a mole" with my monitor until it consents to stay off.

Expected results:
When I type "xset dpms force off", the monitor enters "DPMS off" mode and stays there until I press a key or move the mouse.

Additional info:
I have a Radeon 9550 card, connected via a DVI cable. The monitor is at 1680x1050 resolution, 24 bit depth, and the ATI driver is:

xorg-x11-drv-ati-6.12.2-14.fc11.i586

Comment 1 Chris Rankin 2009-09-19 12:42:53 UTC
I am not running either gnome-screensaver or xscreensaver. This is what "xset q says":

$ xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  auto repeat delay:  500    repeat rate:  30
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 900
  DPMS is Enabled
  Monitor is On

Comment 2 Matěj Cepl 2009-11-05 18:38:11 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 3 Chris Rankin 2009-11-07 13:47:27 UTC
I have just updated to the following packages from updates-testing, and the "wakeup" bug is still present.

Nov 07 13:36:26 Updated: xorg-x11-server-common-1.6.4-0.3.fc11.i586
Nov 07 13:36:27 Updated: xorg-x11-server-Xorg-1.6.4-0.3.fc11.i586
Nov 07 13:36:27 Updated: xorg-x11-server-devel-1.6.4-0.3.fc11.i586
Nov 07 13:43:41 Updated: xorg-x11-drv-evdev-2.2.6-1.fc11.i586

Comment 4 Chris Rankin 2009-11-20 00:45:58 UTC
This bug still happens with minty-fresh Fedora 12.

Comment 5 Chris Campbell 2009-11-22 23:27:49 UTC
(In reply to comment #4)
> This bug still happens with minty-fresh Fedora 12.  

Updating this bug to Fedora 12.

Comment 6 Matěj Cepl 2009-11-26 21:55:47 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 7 Chris Rankin 2009-11-26 22:16:14 UTC
Created attachment 374079 [details]
dmesg log

Comment 8 Chris Rankin 2009-11-26 22:16:44 UTC
Created attachment 374080 [details]
xorg configuration file

Comment 9 Chris Rankin 2009-11-26 22:17:16 UTC
Created attachment 374081 [details]
X server log file

Comment 10 Matěj Cepl 2010-09-30 14:29:24 UTC

*** This bug has been marked as a duplicate of bug 582532 ***


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