Kinfo error: Vulkan apiVersion is 0

Hi, I have a problem, every time I run the kinfo command, here’s what I get:

ERROR:             VkInstanceCreateInfo::pApplicationInfo::apiVersion has value of 0 which is not permitted. If apiVersion is not 0, then it must be greater than or equal to the value of VK_API_VERSION_1_0 [VUID-VkApplicationInfo-apiVersion]  
Operating System: KDE neon 6.3  
KDE Plasma Version: 6.3.4  
KDE Frameworks Version: 6.12.0  
Qt Version: 6.8.2  
Kernel Version: 6.11.0-21-generic (64-bit)  
Graphics Platform: Wayland  
Processors: 20 × 13th Gen Intel® Core™ i7-13700H  
Memory: 31.0 Gio of RAM  
Graphics Processor 1: Intel® Graphics  
Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU  

I don’t really understand where this is coming from. I tried digging a bit using strace, and I can see it’s loading .json files from /usr/share/vulkan/, like VkLayer_MESA_device_select.json and the Intel ones (intel_hasvk_icd.x86_64.json). No config files in .local or in /etc/.

I also tried launching it with QT_DEBUG_PLUGINS=1 or by manually forcing VK_ICD_FILENAMES to the Intel or NVIDIA files, but I still get the same error. Sometimes I also get messages like libEGL warning: egl: failed to create dri2 screen depending on the context.

If anyone has a solution, thanks in advance!

Hi - just double-checking, are you forcing a Vulkan rendering backend for Plasma, by chance? That can be double-checked by opening your Application Launcher and searching for “Plasma Renderer”:

I had to execute it with “kcmshell6 kcm_qtquicksettings”

(all settings are by default on “automatic”)

vulcaninfo runs without a error?

Had something like that since December, every time i ran eglinfo it crashed with libEGL warning: egl: failed to create dri2 screen. After some debugging it looked like something none existent on the nivida side of things was detected and trying to fetch details of that caused it to crash. I never ran kinfo, though.
In my case:

Graphics Processor 1: NVIDIA GeForce RTX 4070 Laptop GPU
Graphics Processor 2: Intel® Graphics  

Apparently, according to the Arch forum, a known bug.
Since the start of February Steam started with a crash at the Hardware detection stage as well probably for the same reason. But as everything (and every Game) still worked I ignored it.

With the updates 2 days ago, unfortunately I can not recall all the packages apart from Kernel 6.14 nothing major, it finally got fixed. But that was on Arch as I already mentioned.

Sorry, I thought I had replied, but it seems that I didn’t, actually…

So yes, these commands vulcaninfo or eglinfo seem to work properly!