Linux - Nvidia specific detection and fixes

[jamincollins]

Description

Without these changes, Linux users with a discrete Nvidia GPU can not see the Home or Project tabs.

In fact attempting to access either of them results in increased CPU utilization and the following output over and over to the console in a loop:

AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer

With these changes, Orca Slicer can reliably detect which GPU it is being run on and set the appropriate environment variables as needed.

Tests

Built and tested on Arch Linux on systems with:

• AMD graphics
• Intel and Nvidia running in Optimus (aka hybrid mode)
• Intel and Nvidia running in discrete mode

In each case the appropriate system was detected and the appropriate settings set.