On Sun, Jan 17, 2010 at 10:25:21 -0800, Russ Allbery wrote: > Julien Cristau <jcris...@debian.org> writes: > > > the diff from 1.7.3.902 to 1.7.4 is quite small[0], and I can't see > > anything in it that would explain this. Are you sure this didn't happen > > with 1.7.3.902? > > Ah, hm, you're correct. I normally suspend rather than restarting the X > server, which means that I could well have been running the X server > before: > > [UPGRADE] xserver-common 2:1.6.5-1 -> 2:1.7.3.902-1 > [UPGRADE] xserver-xorg 1:7.4+4 -> 1:7.5+1 > [UPGRADE] xserver-xorg-core 2:1.6.5-1 -> 2:1.7.3.902-1 > [UPGRADE] xserver-xorg-input-evdev 1:2.2.5-1 -> 1:2.3.2-2 > [UPGRADE] xserver-xorg-input-kbd 1:1.3.2-4 -> 1:1.4.0-1 > [UPGRADE] xserver-xorg-input-mouse 1:1.4.0-4 -> 1:1.5.0-1 > [UPGRADE] xserver-xorg-input-synaptics 1.2.0-2 -> 1.2.1-1 > [UPGRADE] xserver-xorg-video-radeonhd 1.2.5-1 -> 1.3.0-2 > > which happened two days earlier. Sorry about that; I should have thought > a little bit more about that. That makes a great deal more sense. I was > surprised that such a small upgrade could cause this problem. > OK, that would be less surprising :)
> I suspect that this may actually be a bug in the -radeonhd driver, given > that obviously not everyone is seeing this. > It would probably be worth trying radeon instead of radeonhd, then. Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
