I just tagged a 1.1.1 release for libglvnd with the AARCH64 and PPC64LE fixes:
https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.1
If you're switching from 1.0.0, note that the dispatch table order
changed between v1.0.0 and v1.1.0, so you'll need matching builds of
libGLdispatch.so, libOpenGL.
The actual release tag (plus tarball and release notes) is here:
https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1782285
Title:
Add miss
The other libglvnd libraries would already cause a conflict with
nvidia-340, wouldn't they?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1782285
Title:
Add missing libGLESv1_CM.so to Bioni
Liblgnvd has a new 1.1.0 point release, which includes that fix (as well
as an assortment of others).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1780039
Title:
Khronos CTS failure on Bio
Also, while GLESv1 is the fixed-pipeline stuff, libGLESv1_CM.so just
provides a set of forwarder functions. Libglvnd forwards those calls to
a vendor library based on the current context, so it's up to the vendor
library what to do with them. If a vendor doesn't provide a function to
forward to, th
Just because Mesa doesn't provide GLESv1 doesn't mean other vendor
libraries can't. It certainly isn't any reason to prohibit GLESv1
support if a vendor library would otherwise be able to support it.
Conversely, having the full set of libglvnd libraries (including
libGLESv1_CM.so) doesn't require
James Jones is the original author of the patch. I made a couple
modifications to it before attaching it -- some minor simplifications,
adding the config option, slightly better error resilience, and updating
it to work against the latest compiz source tree.
--
You received this bug notification
I've attached a patch with the same fix that should work with compiz
0.9.7.12 in Precise.
** Patch added: "Add the GL_EXT_x11_sync_object to 0.9.7.12"
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/269904/+attachment/3970253/+files/add_x_to_gl_sync_0.9.7.12.patch
--
You received this
Just tested on 13.10, and I can still reproduce the problem. It's less
frequent on my system than it did on 12.04, but it still shows up every
so often.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bu
I don't see any changes that would have fixed it, but it's quite
possible that other changes could adjust the timing such that the bug is
harder to reproduce.
I've got a Q600 handy, though, so give me a few minutes to load up Saucy
onto my test system and I'll check.
--
You received this bug not
This is very likely the same race condition as bug #269904.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/861268
Title:
text corruption in terminals (xterm, urxvt) and emacs
I've attached a patch that fixes the problem.
To give a little more detail on the race condition:
The problem is that when the X server receives a request to do some
drawing, it will send the drawing commands to the video driver and then
it immediately sends out the damage event. That works as lo
12 matches
Mail list logo
