Yes, my problem was like the bug #91064. >From what I could understand the legacy driver can't properly do GLX rendering >with the X protocol extension Composite enabled. So the driver disables it by default (when we have Composite).
# cat /var/log/Xorg.0.log | grep GLX (II) Loading extension GLX (II) Loading extension NV-GLX (EE) GLX is not supported with the Composite extension "Full Composite support will require additional driver support. Currently, direct rendering clients such as GLX have no way of knowing that they are supposed to render into a pixmap, and will draw directly to the screen instead. We are currently investigating what is necessary for such clients to interoperate seamlessly with Composite. In the meantime, GLX will be disabled by default when the Composite extension is detected. An option has been provided to re-enable it. See 'Option "AllowGLXWithComposite"' in (app-d) APPENDIX D: X CONFIG OPTIONS." (from nvidia at http://http.download.nvidia.com/XFree86/Linux-x86/1.0-7184/README/readme.txt) I was just wondering why glxinfo would crash like it did! Apart from this segfault I would say we have a duplicated bug. -- [nvidia-glx-legacy] [apport] glxinfo crashed with SIGSEGV https://bugs.launchpad.net/bugs/83147 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
