Mailinglist Archive: opensuse-bugs (8080 mails)

< Previous Next >
[Bug 197858] X server wakes up on any ACPI event
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 9 Feb 2007 05:18:38 -0700 (MST)
  • Message-id: <20070209121838.E8953FBB@xxxxxxxxxxxxxxxxxxxxxx>

am@xxxxxxxxxxxx changed:

What |Removed |Added
CC| |am@xxxxxxxxxxxx
Resolution|FIXED |

------- Comment #45 from am@xxxxxxxxxxxx 2007-02-09 05:18 MST -------
This bug does not appear fixed (at least in the 10.2 most recent fixes I picked
up from yast last night.

I have chased more explicit info on it (or possibly a variant on it) for my
Toshiba M300 laptop:
sys_vendor = "TOSHIBA"
sys_product = "PORTEGE M300"
sys_version = "PPM30E-00D01QEN"
bios_version = "Version 1.10"

I note the following bad interaction of X and suspend
(which I didn't see reported here explicitly).
1. I fleshly power up, and login directly to FVWM2 (i.e. little messing around)
and xset dpms 0 0 300 (or so).
2. then acpi_events (I use plug/unplug laptop power) then do *not*
cause the backlight to be turned on after DMPS turns off the screen
but they are reported by acpi_listen. Moreover, plug/unplug changes
brightness (before the 300 sec timeout). So X is working 'properly'.
3. However, if I then force suspend with /usr/bin/powersave -u
and then resume then:
4. afterwards acpi events (as reported by acpi_listen) now *do* cause the
backlight to turn on :-( [this has the effect of consuming battery but
not displaying text as X is still blanking the image, so the backlight is
spuriously on.]
5. This effect also happens with powersave -U.

Sorry if this is fixed in 10.3 (but surely it's critical enough to fix in

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >