> Last time I dealt with this stuff bumblebee was still in use.
The primus-vk-nvidia stack still uses Bumblebee. It replaces the original PRIMUS component with a version that shares the image data through the Vulkan APIs, which seems to have fewer issues with incompatible OpenGL versions (even when both the app and the compositor are using OpenGL and not Vulkan). Perhaps something about Vulkan being designed from the start to support multiple vendor backends in the same process, vs. OpenGL where you generally have to load a single vendor's implementation?
The primus-vk-nvidia stack still uses Bumblebee. It replaces the original PRIMUS component with a version that shares the image data through the Vulkan APIs, which seems to have fewer issues with incompatible OpenGL versions (even when both the app and the compositor are using OpenGL and not Vulkan). Perhaps something about Vulkan being designed from the start to support multiple vendor backends in the same process, vs. OpenGL where you generally have to load a single vendor's implementation?