On Tuesday 30 August 2011 15:54:41 Eric Valette wrote: > On 08/30/2011 03:45 PM, Julien Cristau wrote: > > On Mon, Aug 29, 2011 at 21:35:46 +0200, Eric Valette wrote: > >> Package: xserver-xorg-video-nvidia > >> Version: 285.03-1 > >> Severity: normal > >> > >> The new .11 xorg driver ABI has been updated to 11. As the nvidia driver > >> supports it at least enough to be useable via kde4, please add the > >> xorg-video-abi- compatibility. > > > > There's a known issue with nvidia's libglx with that version, so I'm not > > sure it's a good idea quite yet. > > http://lists.x.org/pipermail/xorg-devel/2011-August/024752.html > > I broke my X system with a bogus dist-upgrade and was forced to > reinstall libglx and nvidei xorg driver :-(
Hi, I did a safe-upgrade, which upgraded nvidia-graphics-drivers to 280.13-2, and after reboot, X didn't start (properly). In /var/log/Xorg.0.log I found a/the message about mismatching ABI version. Since I'm subscribed to this list, I was aware of a potential problem (hence the reboot) and therefor was able to quickly find the relevant bug report (639737). That bug report describes how to fix/workaround it ('therefore the "IgnoreABI" option needs to be enabled, see xorg.conf(5)'). (Haven't tried if it worked yet) I do have apt-listbugs installed, but since this bug was/is severity normal (and marked as done) I didn't get a warning or sth like that. I got X working again by downgrading (and holding) to the testing versions of nvidia-kernel-dkms and xserver-xorg-video-nvidia which caused those and related packages to be downgraded: partly snippet from /var/log/aptitude: ================================================================= [DOWNGRADE] libgl1-nvidia-glx 280.13-2 -> 280.13-1 [DOWNGRADE] nvidia-alternative 280.13-2 -> 280.13-1 [DOWNGRADE] nvidia-glx 280.13-2 -> 280.13-1 [DOWNGRADE] nvidia-vdpau-driver 280.13-2 -> 280.13-1 [DOWNGRADE] xserver-xorg-core 2:1.11.0-1 -> 2:1.10.4-1 [DOWNGRADE] xserver-xorg-input-evdev 1:2.6.0-2+b2 -> 1:2.6.0-2+b1 [DOWNGRADE] xserver-xorg-video-nvidia 280.13-2 -> 280.13-1 [DOWNGRADE] xserver-xorg-video-vesa 1:2.3.0-7+b1 -> 1:2.3.0-7 [HOLD] nvidia-kernel-dkms ================================================================= But if I wasn't subscribed to this list, I probably wouldn't have found this bug report and therefor wouldn't have found the workaround. And since this bug is closed and doesn't (didn't) have a high enough severity, apt-listbug didn't issue a warning that the upgrade would make X stop working and/or alerted me to the bug report describing the workaround. Shouldn't there be a warning or sth like that mentioning the workaround when upgrading to 280.13-2? And/or shouldn't this bug be reopened (or sth like that) with a higher severity, so ppl with apt- listbug will get notified and prevents the current version from entering testing? Regards, Diederik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org