Page 2 of 7 FirstFirst 1234 ... LastLast
Results 11 to 20 of 62

Thread: Problem with xset dpms force off

  1. #11
    Join Date
    Nov 2008
    Beans
    6

    Re: Problem with xset dpms force off

    This bug has been reported here: https://bugs.launchpad.net/ubuntu/+s...er/+bug/447728

    See my post in that bug-report for more info on this issue.

  2. #12
    Join Date
    Nov 2009
    Beans
    6

    Re: Problem with xset dpms force off

    I have this problem too, and it doesn't look like there's an easy solution. I have, however, whipped up a quick script to maybe solve this problem for some of you. It's not an ideal solution (you run the script once to turn the screen off, then again to turn it back on), but it'll have to do until the bug gets fixed. Here's a link:
    http://alexcabal.com/turn-your-lapto...ubuntu-karmic/

  3. #13

    Re: Problem with xset dpms force off


  4. #14
    Join Date
    Jan 2010
    Beans
    7

    Re: Problem with xset dpms force off

    It work if I have volume 0% for pulse audio!


    ------
    Sorry false alarm I turn pulse volume on and it steel working... but it does not before...
    Last edited by Andaril; January 19th, 2010 at 05:31 AM.

  5. #15
    Join Date
    Oct 2009
    Beans
    19
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: Problem with xset dpms force off

    Works perfectly fine! Thanks!!!

  6. #16
    Join Date
    May 2010
    Beans
    2

    Re: Problem with xset dpms force off

    I have this same problem with Ubuntu Netbook Edition 10.04 on a Toshiba NB100

  7. #17
    Join Date
    Jun 2007
    Beans
    237

    Re: Problem with xset dpms force off

    Quote Originally Posted by mondalaci View Post
    This doesn't work for me... Somehow the backlight stays off for longer than if I just did xset dpms force off, but it still eventually does after 30 or so seconds...
    Last edited by muadnu; May 24th, 2010 at 04:27 PM.

  8. #18
    Join Date
    Jun 2007
    Beans
    237

    Re: Problem with xset dpms force off

    I think I know what the problem is: gnome-screensaver. If I run
    Code:
    sleep 3 && xset -display :0.0 dpms force off && gnome-screensaver-command -i
    on a terminal (the last bit inhibits the screensaver) then the backlight stays off (at least for a couple of minutes, which is what I've tried). This has the problem that now gnome-screensaver is inhibited even if I turn the screen back on (since it will stay inhibited until I cancel the command, e.g. by closing the terminal or hitting ctrl+c). But maybe someone has a good idea of how to go from here.

  9. #19
    Join Date
    Jun 2006
    Location
    Nux Jam
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Problem with xset dpms force off

    might help to install the latest driver:

    https://launchpad.net/~xorg-edgers/+archive/ppa

  10. #20
    Join Date
    Aug 2008
    Beans
    24

    Re: Problem with xset dpms force off

    Quote Originally Posted by muadnu View Post
    I think I know what the problem is: gnome-screensaver. If I run
    Code:
    sleep 3 && xset -display :0.0 dpms force off && gnome-screensaver-command -i
    on a terminal (the last bit inhibits the screensaver) then the backlight stays off (at least for a couple of minutes, which is what I've tried). This has the problem that now gnome-screensaver is inhibited even if I turn the screen back on (since it will stay inhibited until I cancel the command, e.g. by closing the terminal or hitting ctrl+c). But maybe someone has a good idea of how to go from here.
    Bingo: it's gnome-screensaver. Here's one way to fix this:

    Code:
    sudo apt-get remove gnome-screensaver
    Honestly who needs a stupid "screen saver" anyways, I'm not using a plasma display over here on my laptop, nothing is getting burned in. I just want something to turn off my display, which gnome-power-manager does already. Hopefully this is a better solution than the utterly insane option of running 'xset dpms force off' in an infinite loop.

    Seriously though, people are piddling about with this bug on three different bugtrackers over the course of months and this is the first time someone's pointed out what the actual problem is. Sheesh.
    Last edited by nxmehta; May 25th, 2010 at 07:42 AM.

Page 2 of 7 FirstFirst 1234 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •