| Summary: | Xserver wakes itself up shortly after being put to sleep with "xset dpms force off" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Chris Rankin <rankincj> | ||||||
| Component: | Server/General | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | unspecified | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Chris Rankin
2010-01-04 05:29:26 UTC
Created attachment 32432 [details]
Xorg log file
Created attachment 32433 [details]
xorg configuration file
This is not a driver bug. It is caused by late input events. try: sleep 5; xset dpms force off to make sure all input events have been processed before the monitor is turned off. (In reply to comment #3) > This is not a driver bug. It is caused by late input events. Is there a way to see what these "input events" actually are? Because if they can be *this* late then I would consider that to be a bug in its own right. (Had you suggested that invisible pixies were dancing on the keyboard, I would have been only *slightly* more surprised by your response.) The X server certainly never used to behave this way. (In reply to comment #4) > Is there a way to see what these "input events" actually are? Because if they > can be *this* late then I would consider that to be a bug in its own right. No, usually it's simply the key up event from releasing the enter key. The command can easily be executed faster than a human being can release the key. (In reply to comment #5) > No, usually it's simply the key up event from releasing the enter key. The > command can easily be executed faster than a human being can release the key. Except that the time interval between my pressing Enter and the X server waking up again is of the order of 10 - 20 seconds. That's too large for me to believe that it's the release Event. If that were the case, I would expect it to wake up immediately. (In reply to comment #5) > No, usually it's simply the key up event from releasing the enter key. The > command can easily be executed faster than a human being can release the key. I have just retested this with both the following commands: sleep 5; xset dpms force off sleep 10; xset dpms force off And in both cases, the machine still *always* wakes itself up. Might be an acpi event or something like that. Either way, this isn't a driver bug. (In reply to comment #8) > Might be an acpi event or something like that. Either way, this isn't a driver > bug. How do we ask the driver what is waking it up, then? The driver provides a dpms hook that the X server uses. Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.