Bug#639737: fixed in nvidia-graphics-drivers 280.13.really.275.28-1

[Andreas Beckmann]

[Please keep the bug Cc:ed. Thanks,]

On 2011-09-14 14:04, Maurizio Oliveri wrote:
> They probably already know about this:
> http://www.nvnews.net/vbulletin/showthread.php?t=166025

Posting bugs to the release thread is not a good idea ... what about
creating a new thread with a descriptive title "Rendering errors with
275.28 driver on Xserver 1.11.0, KDE 4.x.y" ... and it took nearly a
week after the initial report of rendering errors with 1.11 until
someone finally attached a nvidia-bug-report.log.gz so that nvidia can
investigate this ...

> xorg's new abi... So what now? It's either a xorg bug for having broken
> abi, or a nvidia bug for not being able to support the new abi...
> Opening a bug for any of them would probably end in a mutual blame...

And not opening a bug won't help fixing it on either side ...

> I just don't see why it's
> considered better to include a not fully working (and older)
> nvidia driver to fix this issue,

Release notes said "Adds Xserver 1.11 support". Nothing about ", but it
does not render properly under 1.11". But there was daily a new bug
report "nvidia driver uninstallable in sid due to xorg-video-abi-11".

> when it just causes a good lack of
> performance (and it's probably just a workaround until a real solution
> is found)... I mean, it's new xorg vs new nvidia (since the 'new
> driver' is actually a patched old release), woudln't it be better to
> leave things as they were (or, at least, warning about the possible
> performance lost when upgrading) until nvidia/xorg come to a really
> working solution?

I didn't know beforehand that it doesn't work properly. Knowing such
things in advance could save me a lot of work :-)
There were no bugs in the bts that would be reopened by going back from
280.xx to 275.xx. So why shouldn't I upload the new release (even if
it's a downgrade) that is supposed to fix a major problem
(installability in sid)?

Andreas