Andreas, that got it. Thanks for sticking with me on this. It's been an issue since 11/4.
Not enough complaints about this, so it probably my one-off. Thanks again. On Mon, Dec 18, 2017 at 11:15 AM, Andreas Beckmann <a...@debian.org> wrote: > Hi, > > I think I found it. You have some cruft MESA libGL that is being used: > > On 2017-12-18 16:14, Chris Manougian wrote: > > /usr/lib/mesa-diverted/x86_64-linux-gnu/: > > total 1172 > > lrwxrwxrwx 1 root root 10 Nov 18 14:31 libGL.so -> libGL.so.1 > > lrwxrwxrwx 1 root root 14 Nov 18 09:01 libGL.so.1 -> libGL.so.1.2.0 > > -rw-r--r-- 1 root root 567624 Nov 9 05:14 libGL.so.1.0.0 > > -rw-r--r-- 1 root root 463424 Apr 25 2017 libGL.so.1.2.0 > > This should fix it: > > ln -sf libGL.so.1.0.0 /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 > rm /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 > > While we try to clean up a lot of libGL.so.* mess from nvidia-installer > (in package nvidia-installer-cleanup), we may not cover your > installation path. And I doubt you want to dig into finding a > reproducible path to get to your setup :-) > > That would also explain the error message, since this is not a GLVND > libGL, it misses some specific entrypoints and therefore the > installation is considered "incomplete". > And it was probably already messed up long before the glx-diversions > package moved the files to /usr/lib/mesa-diverted ... > > > Andreas >