So, in summary: 1) -> it seems there is an issue in unity for not starting in Colin's case, even if unity_support_test tells he's using llvmpipe, needs to be checked upstream
2) we shouldn't export LIBGL_ALWAYS_SOFTWARE=1 to the environment using a checker. Because that means that all software that can't maybe use unity under hw acceleration but can use smaller apps with hw acceleration will be defaulted to llvmpipe. If we set that to the environment with the checker, all applications will be impacted. So unity itself should do the check at initiliziation time, force and reinitialize with this env variable and then unset it. 3 and 4) can't really be dealt with unfortunately -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039155 Title: Unity fails to load on old hardware. Missing automatic fallback to LLVMpipe To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1039155/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
