When screensaver switch display off it never switch on again

Display power management is handled by X - what graphics chipset do you have?

(In reply to comment #1)
> Display power management is handled by X - what graphics chipset do you have?

Please respond; we need more information in order to analyze the problem

Hi,

sorry if I didn't reply earlier. My notebook is Toshiba Satellite M30-742.
The chipset is nVivia GeForce FX 5200 I think.

(In reply to comment #0)
> Hello,
>
> I've this problem: when power management is enabled in xscreensaver and this
> last one switch off my notebook display, it's not possible to turn it on anymore
> (in that session). I've to power off the notebook and to boot again :(

I have de same problem with a via onboard card. My lspci:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400] Chipset Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3
UniChrome] Integrated Video (rev 01)

I can login with ssh, but the display never come back. I don't see any errors en
my logs.

please attach a full /var/log/Xorg.0.log
diego: your problem is separate from this one -- please file a separate bug

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.