Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1930532

Summary: Several demos fail due to missing shaders
Product: Red Hat Enterprise Linux 8 Reporter: Yaakov Selkowitz <yselkowi>
Component: mesa-demosAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: airlied, ajax, extras-qa, goeran, igor.raits, pekopec, tpelka, yselkowi
Target Milestone: rcKeywords: Patch
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1373299 Environment:
Last Closed: 2022-08-19 07:28:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1373299, 1930534    
Bug Blocks:    
Attachments:
Description Flags
Patch for rhel-8.4.0 none

Description Yaakov Selkowitz 2021-02-19 05:30:47 UTC
+++ This bug was initially created as a clone of Bug #1373299 +++

Description of problem:
A number of mesa-demos do not have their shader files installed, causing them to crash when attempting to run them, e.g.:

$ /usr/lib64/mesa/blinking-teapot # or brick, or bump, or...
Unable to open shader file blinking-teapot.vert
Unable to open shader file blinking-teapot.frag
blinking-teapot: shaderutil.c:192: LinkShaders3: Assertion `vertShader || fragShader' failed.
Aborted (core dumped)

Version-Release number of selected component (if applicable):
mesa-demos-8.3.0-3.fc24.x86_64

Additional info:
A source patch is available here, which requires a subsequent autoreconf:

https://raw.githubusercontent.com/cygwinports/mesa-demos/master/8.3.0-glsl-system-data.patch

--- Additional comment from Yaakov Selkowitz on 2016-09-05 17:46:30 CDT ---

In fact, due to not being listed in EXTRA_DIST, a number of shader files are not even in the official tarball.  Using a git snapshot of the tag is required to completely fix this.

Patch forthcoming.

--- Additional comment from Yaakov Selkowitz on 2016-09-05 18:16:02 CDT ---

Note that this requires using a cgit tarball for the sources, as some are 
missing in EXTRA_DIST and therefore not included in the 'make dist' tarball.

Also includes a patch for bug 1018088.

Successful koji scratch build:

http://koji.fedoraproject.org/koji/taskinfo?taskID=15510748

--- Additional comment from Fedora End Of Life on 2017-11-16 12:47:39 CST ---

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

--- Additional comment from Fedora End Of Life on 2018-02-20 09:39:12 CST ---

This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

--- Additional comment from Ben Cotton on 2019-05-02 16:13:55 CDT ---

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Ben Cotton on 2020-04-30 17:08:41 CDT ---

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Ben Cotton on 2020-08-11 10:33:00 CDT ---

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

--- Additional comment from Yaakov Selkowitz on 2021-02-18 23:25:24 CST ---

Updated patch for rawhide.

Comment 1 Yaakov Selkowitz 2021-02-19 05:33:44 UTC
Created attachment 1757990 [details]
Patch for rhel-8.4.0

Comment 4 RHEL Program Management 2022-08-19 07:28:00 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.