I’ve been following an Nvidia bug that’s been affecting me for a while now and am happy to say that its apparently been fixed! I say apparently, because I’ve not been around my Linux box for several days (due to the holidays) and haven’t had a chance to confirm for myself.
If you have an Nvidia card, especially the 7300le model like I have, and have had difficulties using Unity 3D with the proprietary drivers, then you may have experienced this bug: [nvidia, 7300, 7400] display freeze when using unity desktop
Nvidia has just released an update which resolves this issue and it can easily be installed right away!
Release highlights since 275.36:
- Fixed a bug that would cause Firefox to abort on pages with Flash when layers acceleration was force-enabled on Linux and Solaris.
- Fixed a bug that could cause display devices on a secondary GPU to get swapped between X screens when restarting the X server.
- Fixed a regression that caused blank/white windows when exhausting video memory on GeForce 6 and 7 series GPUs while using composited desktops.
- Fixed a bug that caused a crash when glDrawArrays was used with a non-VBO vertex attribute array to draw on a Xinerama screen other than screen 0 using an indirect GLX context.
The 275.43 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86 is available for download via FTP.
The 275.43 NVIDIA Accelerated Linux Graphics Driver Set for Linux/x86_64 is available for download via FTP.
Please note: This NVIDIA Linux graphics driver release supports GeForce 6xxx and newer NVIDIA GPUs, GeForce4 and older GPUs are supported through the 96.43.xx and 71.86.xx NVIDIA legacy graphics drivers. GeForce FX GPUs are supported through the 173.14.xx NVIDIA legacy graphics drivers.
Please also note: If you encounter any problems with the 275.43 NVIDIA Linux graphics driver release, please start a new thread and include a detailed description of the problem, reproduction steps and generate/attach an nvidia-bug-report.log.gz file (please see http://www.nvnews.net/vbulletin/showthread.php?t=46678 for details).
If you’re seeing the same problem and would like to test the update, there are a few specific instructions that you may (or may not) need to follow, posted here.