New comment by dm17 on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-763966039

Comment:
> As far as I know, the VAAPI build option is no longer required in any way. If the hw accel isn't working correctly / being detected, that's a separate issue.

Such a pain to debug chromium. Perhaps Void should consider replacing chromium with its own custom build of ungoogled-chromium... Wouldn't that be truer to the FOSS message anyway (considering how much tracking comes with chromium)?