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

Bug#440802: marked as done (xserver-xorg-video-ati: DPMS + suspend/resume, display never recovers)

Your message dated Sun, 18 Nov 2007 17:21:04 +0100
with message-id <47406670.9020102@ens-lyon.org>
and subject line Bug#440802: xserver-xorg-video-ati: DPMS + suspend/resume, display never recovers
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-xorg-video-ati
Version: 1:6.6.3-2
Severity: normal

I have this device:

00:14.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M (rev 64) (prog-if 00 [VGA])

When I suspend/resume while DPMS is engaged then the X display refuses 
to recover. It is still possible to switch to a different virtual 
console (Ctl-Alt-F1) and that works. The virtual console is visible. X 
can be restored by restarting the display manager.

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

Kernel: Linux 2.6.22.1-b3 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xorg-video-ati depends on:
ii  libc6                  2.6-2             GNU C Library: Shared libraries
ii  xserver-xorg-core      2:1.3.0.0.dfsg-11 X.Org X server -- core server

xserver-xorg-video-ati recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1:6.7.192-1

I am marking this bug as fixed in 6.7.192 (6.7.196 is currently in
experimental) as explained earlier. However, it is not clear
whether the server is involved or not here. The fix could just be
that 6.7.19x uses RandR 1.2 while 6.6.x does not, and the server
could be doing different things for DPMS for these.

Brice

--- End Message ---
Reply to: