Bumblebee is only a workaround. If you use the nvidia gpu with the proprietary drivers with it, it will exhibit the same behaviour if an application uses the nvidia GPU, from what I've heard. Furthermore, Bumblebee does not have perfectly working optimus support. It appears to be bottlenecked somewhere that is not the GPU for me, probably because of virtualgl silliness. I appreciate the hint for anyone who's locking for a sort-of workaround, but I don't think it's time to lose hope just yet.
@bluevector: this is not a problem with opensource (as the nvidia driver is closed source) and it is not a problem with Intel graphics (as the nvidia drivers are causing the problem). It's entirely nvidia's job to fix it, as they've chosen to keep their drivers closed source, and thus forbidden everyone but them to fix the bug. It's entirely a problem caused by proprietary software. Please direct your hate-beams at nvidia.
Bumblebee is only a workaround. If you use the nvidia gpu with the proprietary drivers with it, it will exhibit the same behaviour if an application uses the nvidia GPU, from what I've heard. Furthermore, Bumblebee does not have perfectly working optimus support. It appears to be bottlenecked somewhere that is not the GPU for me, probably because of virtualgl silliness. I appreciate the hint for anyone who's locking for a sort-of workaround, but I don't think it's time to lose hope just yet.
@bluevector: this is not a problem with opensource (as the nvidia driver is closed source) and it is not a problem with Intel graphics (as the nvidia drivers are causing the problem). It's entirely nvidia's job to fix it, as they've chosen to keep their drivers closed source, and thus forbidden everyone but them to fix the bug. It's entirely a problem caused by proprietary software. Please direct your hate-beams at nvidia.