stabilize =x11-drivers/nvidia-drivers-295.20-r1 target keywords: amd64 x86
Please also stabilize latest eselect-opencl: =eselect-opencl-1.1.0-r1 ~amd64 ~x86
amd64 stable
Have you checked comments 5-7 of bug 387079? Perhaps that bug should block this one?
If we prevented stabilization of nvidia-drivers due to an issue in an uncommon setup/configuration, we'd never have a version stable. The next release will fix this but then break something else. It will be a never ending cycle. We don't have to source so we can't create a truly stable branch. As I advise to all users, find a release that works for you and stick with it.
There is some issue with crucial functionality with this driver, though it may be due principally to newer versions of glibc, as discussed here: http://www.nvnews.net/vbulletin/showthread.php?t=176405 and additional forum links contained there. Specifically, vlc segfaults due to some calls within the nvidia driver, making this a release that virtually no-one should choose.
(In reply to comment #5) > There is some issue with crucial functionality with this driver, though it > may be due principally to newer versions of glibc, as discussed here: > http://www.nvnews.net/vbulletin/showthread.php?t=176405 and additional forum > links contained there. > > Specifically, vlc segfaults due to some calls within the nvidia driver, > making this a release that virtually no-one should choose. It has nothing to do with THIS release of nvidia-drivers. The issue has to do with a change inside of glibc 2.15 that causes this release and all releases before it to fail. You'll have to use 295.33 or newer with glibc 2.15 or newer.
It will continue in bug 411617