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.
Created attachment 1469790[details]
test case for reproducing
Description of problem:
Error: XtCreateWidget "glwidget" requires non-NULL widget class
It looks like this is due to the declaration of glwDrawingAreaWidgetClass in GLwDrawA.h, which comes with the mesa-libGLw-devel package. That header has the line:
GLAPI WidgetClass glwDrawingAreaWidgetClass;
And particularly with dynamic linking, if the actual object (glwDrawingAreaWidgetClass) is not found elsewhere, it is assumed to be a definition (since no extern). But then that new variable is NULL.
This has been working well declaring that variable (there are 2 GLAPI WidgetClass variables there) as extern:
extern GLAPI WidgetClass glwDrawingAreaWidgetClass;
Version-Release number of selected component (if applicable):
mesa-libGLw-devel-8.0.0-4
How reproducible:
every time.
Steps to Reproduce:
attaching test case
gcc -c test.c
gcc test.o -L/usr/lib64 -lGLU -lGL -lXm -lXt -lX11 -lGLw -o test
./test
Error: XtCreateWidget "glwidget" requires non-NULL widget class
Actual results:
Expected results:
No error
Additional info:
attaching patch / workaround, not sure if this is the best way to address the issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2019:2120
Created attachment 1469790 [details] test case for reproducing Description of problem: Error: XtCreateWidget "glwidget" requires non-NULL widget class It looks like this is due to the declaration of glwDrawingAreaWidgetClass in GLwDrawA.h, which comes with the mesa-libGLw-devel package. That header has the line: GLAPI WidgetClass glwDrawingAreaWidgetClass; And particularly with dynamic linking, if the actual object (glwDrawingAreaWidgetClass) is not found elsewhere, it is assumed to be a definition (since no extern). But then that new variable is NULL. This has been working well declaring that variable (there are 2 GLAPI WidgetClass variables there) as extern: extern GLAPI WidgetClass glwDrawingAreaWidgetClass; Version-Release number of selected component (if applicable): mesa-libGLw-devel-8.0.0-4 How reproducible: every time. Steps to Reproduce: attaching test case gcc -c test.c gcc test.o -L/usr/lib64 -lGLU -lGL -lXm -lXt -lX11 -lGLw -o test ./test Error: XtCreateWidget "glwidget" requires non-NULL widget class Actual results: Expected results: No error Additional info: attaching patch / workaround, not sure if this is the best way to address the issue.