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

Bug#438969: marked as done (libxrandr2: Restoring the backlight uses inadequate values)



Your message dated Fri, 16 Nov 2007 09:02:04 +0000
with message-id <E1Isx5Q-0001gH-W9@ries.debian.org>
and subject line Bug#438969: fixed in xserver-xorg-video-intel 2:2.2.0-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libxrandr2
Version: 2:1.2.1-1
Severity: normal

I do have a Sony laptop, and I have mapped the function keys controlling
the brightness of the display to a script setting values in
/sys/class/backlight/sony. This works fine both in the console and
within X up to the point where xscreensaver kicks in and sets the
display to DPMS standby, suspend or off mode. After reactivating the
computer the screensaver sets the brightness of the display using the
xrandr extension not to the value the display brightness had before, but
to the value which is still in memory. To make a long story short, xrandr
should check the actual brightness of the display before it is changed.

I am filing this bug against xrandr because the xbacklight tool shows the
same behaviour, so I do not think that this is an xscreensaver problem.
If I am wrong, please feel free to reassign the bug to another package.

Thanks,
Thomas

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.19.2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash

Versions of packages libxrandr2 depends on:
ii  libc6                         2.6-2      GNU C Library: Shared libraries
ii  libx11-6                      2:1.0.3-7  X11 client-side library
ii  libxext6                      1:1.0.3-2  X11 miscellaneous extension librar
ii  libxrender1                   1:0.9.2-1  X Rendering Extension client libra
ii  x11-common                    1:7.2-5    X Window System (X.Org) infrastruc

libxrandr2 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: xserver-xorg-video-intel
Source-Version: 2:2.2.0-1

We believe that the bug you reported is fixed in the latest version of
xserver-xorg-video-intel, which is due to be installed in the Debian FTP archive:

xserver-xorg-video-i810_2.2.0-1_all.deb
  to pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-i810_2.2.0-1_all.deb
xserver-xorg-video-intel-dbg_2.2.0-1_i386.deb
  to pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel-dbg_2.2.0-1_i386.deb
xserver-xorg-video-intel_2.2.0-1.diff.gz
  to pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.2.0-1.diff.gz
xserver-xorg-video-intel_2.2.0-1.dsc
  to pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.2.0-1.dsc
xserver-xorg-video-intel_2.2.0-1_i386.deb
  to pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.2.0-1_i386.deb
xserver-xorg-video-intel_2.2.0.orig.tar.gz
  to pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.2.0.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 438969@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Brice Goglin <bgoglin@debian.org> (supplier of updated xserver-xorg-video-intel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 16 Nov 2007 09:30:26 +0100
Source: xserver-xorg-video-intel
Binary: xserver-xorg-video-i810 xserver-xorg-video-intel-dbg xserver-xorg-video-intel
Architecture: source all i386
Version: 2:2.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Brice Goglin <bgoglin@debian.org>
Description: 
 xserver-xorg-video-i810 - X.Org X server -- Intel i8xx, i9xx display driver
 xserver-xorg-video-intel - X.Org X server -- Intel i8xx, i9xx display driver
 xserver-xorg-video-intel-dbg - X.Org X server -- Intel i8xx, i9xx display driver (debug symbols)
Closes: 420840 438969 439744 443111
Changes: 
 xserver-xorg-video-intel (2:2.2.0-1) unstable; urgency=low
 .
   * New upstream release.
     + Also pull bugfix commit 4a2b0f340357c4ca58dc9586fad1337b83966362.
     + Fix backlight problems on various chipsets,
       closes: #443111, #438969, #439744.
     + Fix some issues with high resolution, closes: #420840.
   * Add myself to Uploaders and remove Branden with his permission.
Files: 
 2070cb05550e964da03af94a25e1f600 1324 x11 optional xserver-xorg-video-intel_2.2.0-1.dsc
 7cab9695a391f07880bf03dba291f6ee 795366 x11 optional xserver-xorg-video-intel_2.2.0.orig.tar.gz
 b739bbdaa7ab1efa1259cf1f9ff8489a 170996 x11 optional xserver-xorg-video-intel_2.2.0-1.diff.gz
 0934158353b9d1b3b57cc3286172e941 145840 oldlibs optional xserver-xorg-video-i810_2.2.0-1_all.deb
 85b4107040628e79cd3c875f4677abf5 318096 x11 optional xserver-xorg-video-intel_2.2.0-1_i386.deb
 ff672ad614913ac37d8accc556e4ec11 1200748 x11 extra xserver-xorg-video-intel-dbg_2.2.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHPVlDRh88F8PcWfoRAvmEAJ9tqaGEjhr60La+AGxVl4sNVEeKzQCffYs3
PW38+7CIGxPrBapZnsLIEMw=
=3s4G
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: