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 1373302

Summary: Several demos fail due to missing shaders
Product: Red Hat Enterprise Linux 7 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: 7.3CC: goeran, yselkowi
Target Milestone: rcKeywords: Patch
Target Release: ---   
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: 2020-12-15 07:45:29 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    
Bug Blocks:    
Attachments:
Description Flags
patch for rhel-7.3 dist-git none

Description Yaakov Selkowitz 2016-09-05 22:48:00 UTC
Same applies to mesa-demos-8.2.0 in RHEL 7.

+++ 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 18:46:30 EDT ---

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.

Comment 1 Yaakov Selkowitz 2016-09-05 22:59:49 UTC
Created attachment 1198023 [details]
patch for rhel-7.3 dist-git

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.

Successful brew scratch build:

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11702793

Comment 3 RHEL Program Management 2020-12-15 07:45:29 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.