monitors wont go to sleep

Bug #273484 reported by Tim Lunn
68
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Confirmed
Medium
Unassigned
Declined for Intrepid by Bryce Harrington

Bug Description

since recent updates to intrepid my monitors will not go to sleep any more. this has started occurring in the last week. not sure which package update has caused it though.

I am using nvidia drivers with twinview setup, I have tried both the current versions of the 173 and 177 branches of the nvidia drivers and still get this problem. unfortunately I cannot try the 'nv' driver as I can get this to work with DVI connections to my monitors for some reason.

I have also noticed that gnome-screensaver does not appear to be working, it fades to a blank screen and then after about 0.5 secs returns to the desktop. not sure if this related to the power management issues though.

#lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

Revision history for this message
Tim Lunn (darkxst) wrote :
Revision history for this message
kulight (kulight) wrote :

i have the same problem also using nvidia 173 but without twin view

Revision history for this message
sordna (sordna) wrote :

I also have the same problem. I am running intrepid alpha6 64bit, and nvidia driver 177.
Im am using an Asus nvidia EN9500GT PCI-E discrete graphics card. My monitor is a Hanns.G HG281D LCD panel with HDMI and D-SUB inputs.
The graphics card has dvi, hdmi, and d-sub outputs. My monitor only goes to sleep properly when I use the dsub connection. When I connect my monitor to the HDMI or DVI ouputs of the graphics card, the monitor does not go to sleep properly. Instead, the monitor shows a "No Signal Input" message, but I guess it's not a complete loss of signal, because the monitor does not go to sleep. If I disconnect the cable or turn off the computer then the monitor goes to sleep. I have tried "xset dpms force standby/suspend/off" and they all have the same effect (monitor's own "signal loss" message screen, but monitor never actually goes to sleep).

Some interesting points: Using the "nv" driver does not have this problem (sleep works properly over both DVI and HDMI connection).

Using a different discrete graphics card (EVGA nvidia 8400GS) I don't have this problem
with either "nv" or nvidia drivers.

I am not using twinview or xinerama, just a single connection to a single monitor.

Revision history for this message
sordna (sordna) wrote :

This bug only occurs using nvidia's driver.
Not sure whether nvidia-glx-177 or nvidia-177-kernel-source is the actual culprit.

Revision history for this message
Tim Lunn (darkxst) wrote :

It seems as a workaround, manually defining meta modes in the Device section of xorg.conf file seems to resolve this issue for me.

Revision history for this message
sordna (sordna) wrote : Re: [Bug 273484] Re: monitors wont go to sleep

My only metamode line was this:
Option "metamodes" "nvidia-auto-select +0+0"

taking it out did not have any effect on the issue.

Here is the monitor/card/screen sections of my xorg.conf:

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "HSD Hanns.G HG281"
    HorizSync 24.0 - 80.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
EndSection

Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 9500 GT"
    Option "NoLogo" "true"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
    EndSubSection
EndSection

Thanks.

On Wed, Oct 8, 2008 at 2:22 PM, Tim <email address hidden> wrote:

> It seems as a workaround, manually defining meta modes in the Device
> section of xorg.conf file seems to resolve this issue for me.
>

Revision history for this message
Tim Lunn (darkxst) wrote :

try adding
Option "metamodes" "1280x1024"

On 10/09/2008 09:21 AM, sordna wrote:
> My only metamode line was this:
> Option "metamodes" "nvidia-auto-select +0+0"
>
> taking it out did not have any effect on the issue.
>
> Here is the monitor/card/screen sections of my xorg.conf:
>
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "Unknown"
> ModelName "HSD Hanns.G HG281"
> HorizSync 24.0 - 80.0
> VertRefresh 56.0 - 75.0
> Option "DPMS"
> EndSection
>
> Section "Device"
> Identifier "Videocard0"
> Driver "nvidia"
> VendorName "NVIDIA Corporation"
> BoardName "GeForce 9500 GT"
> Option "NoLogo" "true"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "Videocard0"
> Monitor "Monitor0"
> DefaultDepth 24
> SubSection "Display"
> Depth 24
> EndSubSection
> EndSection
>
> Thanks.
>
> On Wed, Oct 8, 2008 at 2:22 PM, Tim <email address hidden> wrote:
>
>
>> It seems as a workaround, manually defining meta modes in the Device
>> section of xorg.conf file seems to resolve this issue for me.
>>
>>
>
>

Revision history for this message
sordna (sordna) wrote :

On Wed, Oct 8, 2008 at 4:05 PM, Tim <email address hidden> wrote:

> try adding
> Option "metamodes" "1280x1024"
>

I just tried it and it has no effect except lowering my resolution.
I also tried Option "metamodes" "1920x1200" (to match my monitor's
resolution)
but it has no effect on the monitor suspend. It still won't go to sleep.
This has to be looked at by someone who knowns the nvidia driver internals
well.
Why does the "nv" driver suspend my monitor properly, and "nvidia" does not?

Revision history for this message
sam tygier (samtygier) wrote :

I am seeing the same behaviour on a thinkpad x31 with a radeon 7000 and the radeon driver.

Revision history for this message
sam tygier (samtygier) wrote :

hmmm. the monitor sleeps fine if i disable compiz. maybe thats we you guys are not seeing it with the NV driver. could you try using nvidia with compiz disabled and see if it works?

Revision history for this message
sordna (sordna) wrote :

I have already tried it without compiz, and it did not make a difference for
me. I also tried different window managers
(and no window manager at all, with just xtrem on a plain X screen) and the
monitor still won't go to sleep properly,
either via xscreensaver or via manually doing xset dpms force
standby/suspend/off.

The only thing that solves the problem is going to the free "nv" driver, at
the cost of performance.
I think someone needs to look at the nvidia driver's dpms calls. It's also
strange that
standby/suspend/off have the exact same behavior. I'm guessing all 3 options
result
in the exact same thing done by the nvidia driver. nvidia folks, can someone
look into this?
We want to protect the environment, and dpms needs to work properly !

On Sun, Oct 12, 2008 at 1:54 AM, sam tygier <email address hidden> wrote:

> hmmm. the monitor sleeps fine if i disable compiz. maybe thats we you
> guys are not seeing it with the NV driver. could you try using nvidia
> with compiz disabled and see if it works?
>
>

Revision history for this message
Carlo Di Martino (carlodimartino) wrote :

I can confirm this behaviour with a ATI Radeon 9600. Disabling compiz fixes it for me too.

Revision history for this message
sordna (sordna) wrote :

compiz is not the problem for me.
Only using the "nv" driver, or using Option "UseEDID" "False" with the "nvidia" driver
allows my monitor to sleep properly. Both solutions unacceptable of course.

Revision history for this message
sam tygier (samtygier) wrote :

ok. i think Carlo Di Martino and I have a different issue. I have opened Bug #283904 and subscribed carlo to it (sorry i hope you dont consider this rude).

Revision history for this message
Tim Lunn (darkxst) wrote :

I not so sure that this is a duplicate of that bug,
I initially thought the problem might have been related to the
gnome-screensaver issue, however that seems to be a separate issue/bug.

I think the monitors not sleeping is a problem with the nvidia drivers.

On Thu, 16 Oct 2008 01:13:48 -0000, "Connor Imes" <email address hidden>
said:
> *** This bug is a duplicate of bug 278112 ***
> https://bugs.launchpad.net/bugs/278112
>
> ** This bug has been marked a duplicate of bug 278112
> Screensaver doesn't start
>
> --
> monitors wont go to sleep
> https://bugs.launchpad.net/bugs/273484
> You received this bug notification because you are a direct subscriber
> of the bug.
--
  Tim Lunn
  <email address hidden>

Revision history for this message
sordna (sordna) wrote :

Sorry, but 273484 has NOTHING to do with 278112.
Bug 273484 is NOT about screensaver. It is about power management.
Please remove the duplication. These 2 bugs are not even related to each
other.

sordna

On Wed, Oct 15, 2008 at 6:13 PM, Connor Imes <email address hidden> wrote:

> *** This bug is a duplicate of bug 278112 ***
> https://bugs.launchpad.net/bugs/278112
>
> ** This bug has been marked a duplicate of bug 278112
> Screensaver doesn't start
>

> --
> monitors wont go to sleep
> https://bugs.launchpad.net/bugs/273484
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "nvidia-graphics-drivers-177" source package in Ubuntu: Confirmed
>
> Bug description:
> since recent updates to intrepid my monitors will not go to sleep any more.
> this has started occurring in the last week. not sure which package update
> has caused it though.
>
> I am using nvidia drivers with twinview setup, I have tried both the
> current versions of the 173 and 177 branches of the nvidia drivers and still
> get this problem. unfortunately I cannot try the 'nv' driver as I can get
> this to work with DVI connections to my monitors for some reason.
>
> I have also noticed that gnome-screensaver does not appear to be working,
> it fades to a blank screen and then after about 0.5 secs returns to the
> desktop. not sure if this related to the power management issues though.
>
> #lsb_release -rd
> Description: Ubuntu intrepid (development branch)
> Release: 8.10
>

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

As a starting point, I think it would be useful for those of you experiencing this problem to do the following:

killall gnome-power-manager
gnome-power-manager --no-daemon --verbose 2>&1 gpm.log

Now leave your machine to go idle for as long as it should take the monitor to go in to standby, then attach your log to this bug report.

Thanks

Changed in nvidia-graphics-drivers-177:
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
kimus (kimus) wrote :

My monitor also does not slee, it starts to fade but in the end just awakes.

here is my gpm.log.

note: i had to change a bit the command to get all the logs:
gnome-power-manager --no-daemon --verbose 2>&1 1> gpm.log

Revision history for this message
kimus (kimus) wrote :

is working in the latest update of intrepid

Revision history for this message
sordna (sordna) wrote :

Seems this is not related only to the nvidia driver, from people's reports.

Revision history for this message
YoBoY (yoboy-leguesh) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
Paul O'Keefe (pbokeefe) wrote :

I had other problems once I upgraded to the Jaunty pre-release and ended up switching graphics cards. I do not have a suitable test site any longer to review the problem.
------Original Message------
From: YoBoY
Sender: <email address hidden>
To: <email address hidden>
ReplyTo: Bug 273484
Subject: [Bug 273484] Re: monitors wont go to sleep
Sent: Mar 16, 2009 11:31 AM

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.

--
monitors wont go to sleep
https://bugs.launchpad.net/bugs/273484
You received this bug notification because you are a direct subscriber
of the bug.

Status in Ubuntu: Incomplete

Bug description:
since recent updates to intrepid my monitors will not go to sleep any more. this has started occurring in the last week. not sure which package update has caused it though.

I am using nvidia drivers with twinview setup, I have tried both the current versions of the 173 and 177 branches of the nvidia drivers and still get this problem. unfortunately I cannot try the 'nv' driver as I can get this to work with DVI connections to my monitors for some reason.

I have also noticed that gnome-screensaver does not appear to be working, it fades to a blank screen and then after about 0.5 secs returns to the desktop. not sure if this related to the power management issues though.

#lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10

Sent from my BlackBerry

Revision history for this message
Martin G Miller (mgmiller) wrote :

I have 3 systems running Karmic. 2 are clean installs, one is 64 bit, the other 32. In both of those power management works correctly to shut off the monitors.

My 3rd system is an upgrade from Jaunty. It is 32 bit running on an AMD tripe core with 4 gig ram and nvidia 8600GT using the Nvidia 185.13.36 driver from the Hardware Drivers utility.

This system is on 24/7 and I have the screen saver set to trigger after 5 mins. and then power manager should shut off the display after 10 mins. It functioned correctly in Jaunty.

After the upgrade to Karmic release candidtate, it continued to work correctly for a few days and then the power management stopped shutting of the monitor. The screen saver kicks in as expected, but the monitor never goes to sleep.

System monitor shows that gnome-power-manager is "sleeping".

If I issue the commands :
killall gnome-power-manager
gnome-power-manager
it will work correctly as long as the terminal window is open.

I also found if I killall gnome-power-manager and then log off and back on, it will work as expected, but on a reboot, it returns to its non-working behavior until I kill it and log off and back on.

This behavior is very consistent and happens on every reboot.

Revision history for this message
Aaron Larson (aaronpublic) wrote :

My problem is essentially the same as Martin M's 3rd system. I have a machine that has been upgraded (several times) and is now running Karmic (ubuntu). nvidia 185, dual monitor configuration. My monitors get into screen saver, but never turn off. I haven't tried the killall three step, but I can if that would help diagnose things.

Revision history for this message
Martin G Miller (mgmiller) wrote :

This is an update to my post #23.
My work around for this is now to simply log off and log back on after rebooting. Since I rarely restart this machine, I don't have to do this very often. I found that I do not have to do the killall gnome-power-manager step, just log off and back on and it works.

Revision history for this message
SabreWolfy (sabrewolfy) wrote :

Confirmed in updated Ubuntu Karmic with NVidia version 190.53 and two monitors. Screen saver (blank screen) and power off both set to 5 minutes. Manually locking screen with hotkey also blanks the screen but does not power them off. I'm sure it worked in Jaunty and in Karmic earlier? Executing "xset dpms force suspend" powers off the screens.

Revision history for this message
SabreWolfy (sabrewolfy) wrote :
Revision history for this message
Boris Burtin (boris-burtin) wrote :

I tried running gnome-power-manager on the command line as described in Comment #17. DPMS doesn't kick in and the command generates no output. If I run

xset +dpms
xset dpms 0 0 600

My monitor sleeps after 10 minutes.

Revision history for this message
Delmir (delmir) wrote :

I have this same problems for years with the same LCD monitor using different releases of ubuntu and different computers. The monitor is ACER X233H, and it will simply display a grey box showing "cable not connected" when it should be off. Issuing "xset dpms force off" will bring that "cable not connect" right away. Could it be anyway related to bad BIOS' ACPI settings? This is a long going issue. Can we raise this ticket somehow?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
J.G. (j.gorski)
Changed in ubuntu:
status: Expired → Confirmed
affects: ubuntu → gnome-power-manager (Ubuntu)
Revision history for this message
Zach Sadecki (zsadecki) wrote :

Everything worked fine for me until an upgrade about a week ago. I'm using Gnome Shell on Oneiric. Now the screen will go black, leaving the panel visible, but the monitor no longer powers off.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.