Bug 2418077 - vkcube --validate fails on Fedora 42 with "vkGetDeviceProcAddr(): pName is trying to grab vkCreateDisplayPlaneSurfaceKHR which is an instance level function"
Summary: vkcube --validate fails on Fedora 42 with "vkGetDeviceProcAddr(): pName is tr...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 42
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-01 19:00 UTC by Adam Williamson
Modified: 2026-06-10 15:10 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-10 15:10:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2025-12-01 19:00:24 UTC
As a consequence of the broken mesa update last week, I've added an openQA test which runs `vkcube --validate --c 10` to check Vulkan layers are working correctly.

With the fixes for the bad backport, this test is now running and passing (not crashing) on Fedora 43 and Rawhide. However, it's failing on Fedora 42. It's not crashing the way it was on F43 and Rawhide with the bad backport; it seems to run to conclusion and exit in an orderly fashion. But it prints a warning and exits 1, not 0.

This is the warning:

WARNING : VALIDATION - Message Id Number: 582089644 | Message Id Name: WARNING-vkGetDeviceProcAddr-device
    vkGetDeviceProcAddr(): pName is trying to grab vkCreateDisplayPlaneSurfaceKHR which is an instance level function

Is it possible to make this check pass on Fedora 42, or is there an alternative check we can use that will pass?

If not, I can either bypass the test on F42 entirely, or special-case it so it passes if the exit code is 1 and the output matches this case, though making it still fail if the output has this warning *and* some other message might be tricky.

Comment 1 Fedora Release Engineering 2026-05-06 15:25:08 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2026-06-10 15:10:51 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.