void-linux / void-linux/void-packages
intel_icd.i686.json installed from incorrect package
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.1.10_1 x86_64-musl GenuineIntel uptodate rrnFFF
Package(s) Affected
mesa-vulkan-intel, mesa-vulkan-intel-32bit
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
The /usr/share/vulkan/icd.d/intel_icd.i686.json manifest file would be install along side the shared library it references.
Actual behaviour
The /usr/share/vulkan/icd.d/intel_icd.i686.json file is installed with the mesa-vulkan-intel package while it references the shared library /usr/lib32/libvulkan_intel.so, a library that is installed with the mesa-vulkan-intel-32bit package. This package is not available on musl systems.
Steps to reproduce
- Install
Vulkan-Tools - Run
vkcube --validateon a system withoutmesa-vulkan-intel-32bitinstalled - Observe the error loading
/usr/lib32/libvulkan_intel.so
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the package definitions for mesa-vulkan-intel and mesa-vulkan-intel-32bit, then trace where intel_icd.i686.json and libvulkan_intel.so are assigned. Confirm the manifest is shipped with the package providing its referenced library and rerun the vkcube --validate reproduction without mesa-vulkan-intel-32bit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100