Bug 466011 - vulkaninfo package missing from Neon User repos
Summary: vulkaninfo package missing from Neon User repos
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-18 16:44 UTC by Eridani Rodríguez
Modified: 2025-09-20 09:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eridani Rodríguez 2023-02-18 16:44:59 UTC
SUMMARY
***
kinfocenter has a new page to see Vulkan information inside the Graphics section, but when I navigate to it displays a message saying that “The vulkaninfo tool is required to display this page but could not be found” suggesting the user to search and install it using the package manager. 

However, such search returns no results.

***

OBSERVED RESULT
No vulkaninfo package in Neon user repos.

EXPECTED RESULT
vulkaninfo should be available.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8


ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2023-02-20 14:10:12 UTC
Install vulkan-tools package.
Comment 2 Jonathan Riddell 2023-02-21 10:26:39 UTC
Thanks, I added in the dep now, will be included in the next snapshot
https://invent.kde.org/neon/kde/kinfocenter/commit/723f9dd426729df7e7b56c17868d08ce42a30cfe
Comment 3 Carlos De Maine 2025-09-20 09:35:47 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!