Your message dated Tue, 12 Oct 2010 20:26:53 +0200
with message-id <20101012182652.gn2...@radis.liafa.jussieu.fr>
and subject line Re: Bug#599941: /usr/bin/xset: xset dpms etc seems to operate
on all screens rather than just those provided such as :0.1, in X zaphod mode
has caused the Debian Bug report #599941,
regarding /usr/bin/xset: xset dpms etc seems to operate on all screens rather
than just those provided such as :0.1, in X zaphod mode
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 ow...@bugs.debian.org
immediately.)
--
599941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x11-xserver-utils
Version: 7.3+5
Severity: normal
File: /usr/bin/xset
My xorg.conf is set up to have dpms enabled on one screen (:0.1 -- I'm
using zaphod mode, so :0.0 is a separate screen to :0.1), but disable
on another screen (:0.0, a status screen that must always remain on).
This works, as is expected. However, if I say:
DISPLAY=:0.1 xset dpms 1200 2400 3600
Then it affects :0.0 as well (even though xorg.conf says that screen
has DPMS disabled!). It should only affect the asked for display.
Perhaps it should affect all displays if I was trying to talk to :0
rather than :0.0.
Those not using zaphod mode, but using xinerama mode instead,
obviously would have only the one DISPLAY, and thus xset should affect
them all.
-- System Information:
Debian Release: 5.0.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages x11-xserver-utils depends on:
ii cpp 4:4.3.2-2 The GNU C preprocessor (cpp)
ii libc6 2.7-18lenny4 GNU C Library: Shared libraries
ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library
ii libsm6 2:1.0.3-2 X11 Session Management library
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxau6 1:1.0.3-3 X11 authorisation library
ii libxaw7 2:1.0.4-2 X11 Athena Widget library
ii libxext6 2:1.0.4-2 X11 miscellaneous extension librar
ii libxi6 2:1.1.4-1 X11 Input extension library
ii libxmu6 2:1.0.4-1 X11 miscellaneous utility library
ii libxmuu1 2:1.0.4-1 X11 miscellaneous micro-utility li
ii libxrandr2 2:1.2.3-1 X11 RandR extension library
ii libxrender1 1:0.9.4-2 X Rendering Extension client libra
ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii libxtrap6 2:1.0.0-5 X11 event trapping extension libra
ii libxxf86misc1 1:1.0.1-3 X11 XFree86 miscellaneous extensio
ii libxxf86vm1 1:1.0.2-1 X11 XFree86 video mode extension l
ii x11-common 1:7.3+20 X Window System (X.Org) infrastruc
x11-xserver-utils recommends no packages.
x11-xserver-utils suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Oct 13, 2010 at 03:13:24 +1100, Tim Connors wrote:
> Package: x11-xserver-utils
> Version: 7.3+5
> Severity: normal
> File: /usr/bin/xset
>
> My xorg.conf is set up to have dpms enabled on one screen (:0.1 -- I'm
> using zaphod mode, so :0.0 is a separate screen to :0.1), but disable
> on another screen (:0.0, a status screen that must always remain on).
>
> This works, as is expected. However, if I say:
>
> DISPLAY=:0.1 xset dpms 1200 2400 3600
>
> Then it affects :0.0 as well (even though xorg.conf says that screen
> has DPMS disabled!). It should only affect the asked for display.
> Perhaps it should affect all displays if I was trying to talk to :0
> rather than :0.0.
>
> Those not using zaphod mode, but using xinerama mode instead,
> obviously would have only the one DISPLAY, and thus xset should affect
> them all.
>
The dpms timeouts are global to the X server, not per screen.
Similarly, DPMSEnabled is a global boolean flag. I don't think there's
a bug here.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
