Arch Linux

rado84

Banned

From: Sofia, Bulgaria

Registered: 2019-05-12

Posts: 135

[sort-of-solved] Discord crashing upon system resume from suspend

Topic update: I found the problem - it's with libva. Running discord via terminal displays this error at the same moment discord crashes:

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

The only way to workaround the problem is to disable hardware acceleration in discord and all apps that use/depend on libva. Currently I'm trying to find a way to report this problem to intel cuz it seems that they're the developers of libva but how long will it take for it to be fixed, I can't say.

Hi, everyone.
I tried talking to the Discord support about this but they're as "useful" as Microsoft's suport, meaning it would be better if I can find a "cure" for the problem on my own without their help.
This should be easy to reproduce for anyone. I just need to know if anyone with Arch is experiencing the same problem or is it just local for my system.
The problem is that if I put the system to sleep while Discord is running in the background and then wake it back up, within 10 seconds Discord crashes and closes itself, thus I have to start it manually.

So I'm asking you to try the same and tell me if it crashes on your system and if you have ever had this problem with Discord in the past, how did you cure it?

I tried their "stable" edition (nothing stable about it, though, trust me), I tried reinstalling Discord, I even deleted its entire config directory to see if starting over with clean config will change anything. Well, it did not, Discord is still crashing when I wake the system up, so I'm out of ideas what else to try.

Someone on the internet suggested that the kernel might be involved, altough I don't see how but still I loaded the rolling kernel (normally I'm using the current LTS kernel) and Discord still crashed.
My computer build is in my signature.

Last edited by rado84 (2023-05-08 15:04:24)

---

Core i7-4770, GTX 1660 Ti, 32 GB RAM, Arch 6.x LTS, Cinnamon 5.2.7, GDM

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,202

Re: [sort-of-solved] Discord crashing upon system resume from suspend

Topic update: I found the problem - it's with libva. Running discord via terminal displays this error at the same moment discord crashes:

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

The only way to workaround the problem is to disable hardware acceleration in discord and all apps that use/depend on libva. Currently I'm trying to find a way to report this problem to intel cuz it seems that they're the developers of libva but how long will it take for it to be fixed, I can't say.

This sounds like it could be due to a configuration error on your system .

Post the output of vainfo (comes with libva-utils) and read https://wiki.archlinux.org/title/Hardwa … celeration thoroughly .

Last edited by Lone_Wolf (2023-05-09 10:15:54)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

kzna

Member

Registered: 2023-05-22

Posts: 1

Re: [sort-of-solved] Discord crashing upon system resume from suspend

was getting the same error, however disabled hardware acceleration didn't fix it.

after checking ~/.config/discord/settings.json, i noticed that the resolution width and height had been set to 65536 so i changed it to something normal (1920, 1080) and it seemed to have fix the issue in my case

ypoluektovich

Member

Registered: 2011-11-10

Posts: 17

Re: [sort-of-solved] Discord crashing upon system resume from suspend

I have the same problem as OP. Disabling hardware acceleration in Discord fixed the crashes.

vainfo output:

Trying display: wayland
Trying display: x11
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
vaInitialize failed with error code -1 (unknown libva error),exit

VDPAU seems to work though. I use NVIDIA proprietary drivers.

I haven't touched graphics config in years. Just one day updated the system and the crashes started.

Last edited by ypoluektovich (2023-08-30 17:44:14)