Comment 6 for bug 988079

Hi Thomas,

The .40 nvidia driver was a security fix to close a direct memory access flaw. Unfortunately by disabling that interface it caused a few regressions for certain hardware and/or certain applications, such as (I strongly suspect) this problem you're seeing. An updated driver was released by NVIDIA about a week ago; we're still in process of getting it available in all past ubuntu versions but I think it is now available in Precise's via jockey driver updates. Since it reportedly addresses a lot of the regressions that turned up I would suggest putting that on your test machine to see if that will resolve some or all of the issues you've seen. If so, then no need for any further information beyond that. Let me know if you need any special assistance getting that update made available for your systems.

If there are still issues with that updated driver, then we will need further information so we can escalate the issue with NVIDIA. In general they want to have the nvidia-bugreport.sh script executed to generate the bug data they need. As of precise, the xorg apport hook now collects this information in new bug reports, so filing bug reports with us using 'apport xorg' is our recommended way of filing bugs. Note that you can run this command even on systems where the automatic apport reports have been disabled.

In fact, because we have quite a few basic diagnostics built into the apport hook, we tend to not look at bug reports which were not filed using that tool (i.e. our queues and reports only include bugs filed using apport). So, if policy prohibits running apport in general, I'd still like to arrange a robust way for you to escalate bugs to us as priorities so please contact me directly (<email address hidden>) and we can sort out a good solution.