Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Vulkan: driver name of a previous device is concatenated on multi-GPU systems

Closed Beginner friendly
  • Is something wrong?
#2,619 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
c
Domain
cli

Research direction

Start in src/detection/vulkan/vulkan.c, reading detectVulkan and applyDriverName alongside the existing overwrite comment. Reproduce with fastfetch -s vulkan --pipe -l none on a multi-GPU system, then verify that the displayed driver name is only that of the device with the highest API version and is not concatenated with an earlier device name.

Written by the indexing model from the issue text.

Description

  • I have checked the FAQ but the issue is not covered
Description

On a system with two Vulkan devices, the Vulkan module prints the driver names of both devices glued together:

$ fastfetch -s vulkan --pipe -l none
Vulkan  1.4.354 - NVIDIA [615.71.09]radv [Mesa 26.2.2-arch1.1]

Expected: radv [Mesa 26.2.2-arch1.1], the driver of the device with the highest API version.

In detectVulkan (src/detection/vulkan/vulkan.c), the comment says the driver name should be overwritten whenever a device with a higher API version is found:

// If the device api version is higher than the current highest device api version, overwrite it
// In this case, also use the current device driver name as the shown driver name

However, applyDriverName only appends to result with ffStrbufAppendS and never clears it first. The NVIDIA device is enumerated first and sets the name. The RADV device comes second with a higher API version, and its name is appended to the NVIDIA one instead of replacing it.

As far as I can tell this has been the case since the Vulkan module was added. It only shows up when the device with the highest API version is not the first one enumerated.

A PR with the fix follows: it clears the buffer at the start of applyDriverName.

Version used: fastfetch 2.68.1 (Arch package); also reproduced on dev @ 9801d89 built from source
Bug prevalence: Always
Regression: No
Installation: Package manager
Package manager: pacman

System information
OS      Arch Linux (rolling), kernel 6.18.52-1-lts, x86_64
GPU 1   AMD Raphael [Integrated]   (Vulkan driver: radv, Mesa 26.2.2)
GPU 2   NVIDIA GeForce RTX 5060 [Discrete]   (Vulkan driver: NVIDIA 615.71.09, nvidia-open)
Dominant language
C
Stars
24.8k
Forks
908
Avg merge
22h 1m
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fastfetch-cli/fastfetch

All issues in fastfetch-cli/fastfetch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.