Bug#149650: marked as done (xserver-xfree86: [ati/atimisc] LCD backlight level mismanaged on Mach64 LB rev 220)
Your message dated Wed, 20 Jun 2007 20:08:18 +0200
with message-id <46796D12.80806@ens-lyon.org>
and subject line Bug#149650: xserver-xfree86: [ati/atimisc] LCD backlight level mismanaged on Mach64 LB rev 220
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: xserver-xfree86
Version: 4.1.0-16
I am running woody on a notebook with this videocard:
ATI Technologies Inc 3D Rage LT Pro AGP-133 (rev dc)
While I got fewer troubles with this card with each new
release of the X-packages I now have a problem which seems
to be new:
When the notebook is inactive for a longer time, the LCD-panel's
backlight is not restored correctly after resuming from the
X-screensaver (I mean the default screen-blanking of X after a while of
inactivity) . I have not configured any other screensaver.
What actually happens is that when I move the mouse or hit a key
after a long time of "black-screen) the panels nacklight shorty
lightens an then falls back to black. I think that its just the state
of the backlight which is handled incorrectly here. Interestingly
this happens only when a really long time passed after the
xserver blanked the screen.
Branden, if its unclear what I want to say, please contact me!
Thanks,
Olaf
(possibly this is a known bug which is already fixed in 4.2?)
--
"Jazz is not dead, it just smells funny!" Frank Zappa
--- End Message ---
--- Begin Message ---
Olaf Stetzer wrote:
> Uh, ohh. I still have that laptop but I do not use it anymore. I cannot
> remember that I had this problem in the last years I used it but I cannot
> tell anymore which server or driver I used then. I think it is safe to
> close the
> bug if noone else has reported something similar...
>
> Cheers,
>
> Olaf
Ok, closing then, thanks for the quick reply.
If anybody ever reproduces this problem, feel free to reopen.
Brice
--- End Message ---
Reply to: