4 ms·
This kind of thing usually tends to be some sort of configuration error. Rare these days, but not entirely unheard of, and more likely if you build drivers from
by atq2119 6y ago
This kind of thing usually tends to be some sort of configuration error. Rare these days, but not entirely unheard of, and more likely if you build drivers from source.
- pjmlp 6y agoI don't build drivers from source. If it is a configuration error, Canonical has been making the error since it decided to replace fxgl drivers.