-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot launch firefox with nvidia driver version 525, failed to initialise VAAPI connection #128
Comments
what's your nvidia driver version, I'd to rollback to 520 from 525. Can't find why with the new version vaapi doesn't work |
Do you know what stuff i need to downgrade other than the driver itself? I'm on arch linux |
after downgrading it works, tahnks |
Since the problem has not been fundamentally resolved, I think it is better to reopen this issue? |
I mean, sure. This is just anything but a quickfix but i dont have the first idea why with the new version of nvidia drivers fails... maybe they changed something on cuda since they added support for the new graphics? I think I've read something on the drivers changelog |
This issue is a duplicate of #126. The root issue is one of the CUDA-EGL interop methods we use is failing with the new driver. There doesn't appear to be any way around this, other than to use the direct-backend branch of this library, which is very experimental at the moment. |
When i try and lauch firefox from console, i get this error:
This happened after i tried installing the driver, anyone know why?
The text was updated successfully, but these errors were encountered: