Skip to content
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

libva error: va_getDriverName() failed with unknown libva error,driver_name=(null), Spotify #693

Open
jskuzmenko opened this issue Mar 6, 2023 · 2 comments

Comments

@jskuzmenko
Copy link

I launch Spotify, it hangs. I will write the command spotify --disable-gpu:

libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)

(spotify --disable-gpu:3962): Gtk-WARNING **: 12:40:42.260: Theme parsing error: gtk.css:1422:23: 'font-feature-settings' is not a valid property name

(spotify --disable-gpu:3962): Gtk-WARNING **: 12:40:42.266: Theme parsing error: gtk.css:3308:25: 'font-feature-settings' is not a valid property name

(spotify --disable-gpu:3962): Gtk-WARNING **: 12:40:42.268: Theme parsing error: gtk.css:3770:23: 'font-feature-settings' is not a valid property name

@rubyFeedback
Copy link

I get a very similar error:

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

No clue how to debug it.

mesa version is 23.1.1, glibc 2.37, libva is 2.18.0.

Perhaps these warnings could become better in the long run - they kind of spam into the terminal
and I'd happily try to help solve it, but right now I simply have absolutely no idea how they relate
to the system. (I think I am using the nvidia proprietary code from manjaro; my graphics card
is NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)).

@rubyFeedback
Copy link

rubyFeedback commented Jun 11, 2023

Ah - one immediate improvement I would like to suggest is for that libva error to show the
context. I believe it is due to my browser (thorium, aka chrome-based) and perhaps some
video (I am constantly watching or listening to youtube videos in the background), but
I really don't know (I start thorium from KDE konsole, commandline, typically).

So if possible, perhaps you guys could add a bit more information to this? Such as the
program that triggered this and the overall context. It's ok to use an additional sentence
there, C hackers often love super-simple messages. I love clear and precise messages that
try to be helpful to non-C hackers too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants