Comment 249 for bug 95444

Nominally, this bug can be fixed with a trivial merge of nvclock 0.8b4 from Debian. I've attached the (filtered for autogenerated content) debdiff for this relative to the version currently in jaunty.

There are some practical issues with doing this merge right now, though:
- The reason the new version of nvclock fixes this bug is specifically because it begins to ship smartdimmer, which was previously in a separate package; I understand that the nvclock smartdimmer fixes the issue for GeForce8/9, but I don't know what the risk of regression is for other hardware supported by the previous package, which we will now be Conflicting/Replacing/Providing.
- I have no hardware on which I can test this package.
- We have to replace the current 'smartdimmer' package in main with the new one from nvclock, which requires a review by the ubuntu-mir team. Initial response from the ubuntu-mir team is that they would like to see the Debian merge done first, and only afterwards evaluate it for inclusion in main.

I'm subscribing motu-release for a second opinion on whether this is ok to upload for jaunty. It would be nice to close out this long-standing bug, I just don't know that the risk of regression is appropriate at this point in the release cycle.