Severe Lutris startup lag traced to vulkaninfo calls

Hey,

after updating Lutris from 0.5.21 to 0.5.22, I experienced severe whole-system lag on Lutris startup and when installing games via script.

I downgraded the Lutris client back to 0.5.21, but there was no change. So I assumed it might be runtime-related and dug into it a bit.

First I tried different parameters on startup to single out a cause.

First:

env LUTRIS_RUNTIME=0 lutris -d

to disable the runtime. No effect.

Secondly:

env VK_LOADER_DRIVERS_DISABLE='*dzn*' LUTRIS_RUNTIME=0 lutris -d

to exclude the DZN Vulkan ICD. No effect.

Thirdly:

env VK_LOADER_DRIVERS_SELECT='*nvidia*' LUTRIS_RUNTIME=0 lutris -d

to restrict Vulkan to the NVIDIA ICD. Again, no effect.

I then timed several calls, including Vulkan-related ones, and measured roughly ~6 seconds of delay from vulkaninfo calls specifically.

After making vulkaninfo non-runnable (chmod a-x), I got an error on Lutris startup, as expected:

Command 'vulkaninfo' not found on your system

But the lag was gone. Entirely. No lag when starting Lutris and no lag when adding/installing a game.

It seems that Lutris is making multiple calls to vulkaninfo during startup, and those calls appear to be what causes the lag on my system.

Since downgrading the Lutris client itself did not change the behavior, this seems to have been introduced somewhere in the broader update from the 0.5.21 setup to 0.5.22 and its accompanying packages.

My system runs PikaOS with kernel 7.1.8-pikaos, and I have two GPUs:

• NVIDIA GeForce RTX 4070 Ti
• Intel UHD Graphics

The graphics drivers were updated alongside the Lutris/package update.

Thanks for taking a look. I hope this helps someone else who may be experiencing similar issues.