[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#512614: marked as done (xset dpms rejects reasonable values as illegal)

Your message dated Sun, 13 Jul 2014 15:16:08 +0200
with message-id <20140713131608.GA1598@betterave.cristau.org>
and subject line Re: Bug#512614: xset dpms rejects reasonable values as illegal
has caused the Debian Bug report #512614,
regarding xset dpms rejects reasonable values as illegal
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
512614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512614
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: x11-xserver-utils
Version: 7.3+5



SUMMARY:
xset blanking delays occur in series not parallel
xset dpms 30 60 90 means a total of 180 sec before monitor off
thus xset dpms 90 60 30 should also be legal -- but it is not



Hi!

$ xset dpms <seconds> <seconds> <seconds>

sets the delay before X turns your monitor to standby mode, to
suspend mode, and then off.

Pretty simple.  Seems to work fine too.  Sample output:

$ xset dpms 30 60 90
$ while true; do echo "`date +%T` `xset -q | grep Monitor`";
sleep 10; done
00:59:01   Monitor is On
00:59:11   Monitor is On
00:59:21   Monitor is On
00:59:31   Monitor is in Standby
00:59:41   Monitor is in Standby
00:59:51   Monitor is in Standby
01:00:01   Monitor is in Standby
01:00:11   Monitor is in Standby
01:00:21   Monitor is in Standby
01:00:31   Monitor is in Suspend
01:00:41   Monitor is in Suspend
01:00:51   Monitor is in Suspend
01:01:01   Monitor is in Suspend
01:01:11   Monitor is in Suspend
01:01:21   Monitor is in Suspend
01:01:31   Monitor is in Suspend
01:01:41   Monitor is in Suspend
01:01:51   Monitor is in Suspend
01:02:01   Monitor is Off
01:02:11   Monitor is Off
01:02:21   Monitor is Off
01:02:31   Monitor is On
^C
$

Note that it took exactly 30 seconds to reach standby, 60 seconds
AFTER THAT to reach suspend, and then ANOTHER ADDITIONAL 90
seconds
before the monitor turned off.  Great, I get it, now I know how
to ask for what I really want.

So!  Suppose we want X to wait three minutes before standby and
then 30 seconds each before suspend and off?

$ xset dpms 180 30 30
illegal combination of values
  standby time of 180 is greater than suspend time of 30

Oh no!

OK, this is not of earth-shattering importance, but on the other
hand it should be really easy to fix.

Thanks!

--- End Message ---
--- Begin Message --- 
On Thu, Jan 22, 2009 at 01:46:30 -0800, test123@riseup.net wrote:

> Package: x11-xserver-utils
> Version: 7.3+5
> 
> 
> 
> SUMMARY:
> xset blanking delays occur in series not parallel
> xset dpms 30 60 90 means a total of 180 sec before monitor off
> thus xset dpms 90 60 30 should also be legal -- but it is not
> 
Copying from the upstream bug at
https://bugs.freedesktop.org//show_bug.cgi?id=3041

"xset checks the parameters just so that it can give a more friendly error
message than the BadValue you'd get from sending them to the Xserver,
which does the same check:

static int
ProcDPMSSetTimeouts(ClientPtr client)
{
    REQUEST(xDPMSSetTimeoutsReq);

    REQUEST_SIZE_MATCH(xDPMSSetTimeoutsReq);
    if ((stuff->off != 0)&&(stuff->off < stuff->suspend)) 
    {
        client->errorValue = stuff->off;
        return BadValue;
    }
    if ((stuff->suspend != 0)&&(stuff->suspend < stuff->standby))
    {
        client->errorValue = stuff->suspend;
        return BadValue;
    }  

But I've always believed these are appropriate because they are relative to
the same baseline, the last input event - if they're being treated as relative 
to the previous timeout, that would be a bug in the X server, but the xset 
checks are not."

Closing as not an xset bug.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: