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.
Description of problem:
Getting following error in my journal quite often:
Jul 09 12:43:50 t470s org.gnome.Shell.desktop[10783]: [12002:12002:0709/124350.550020:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Version-Release number of selected component (if applicable):
gnome-shell-3.32.2-4.el8
mutter-3.32.2-5.el8
How reproducible:
100%
Steps to Reproduce:
1. not sure just appear in journal
2.
3.
Actual results:
Expected results:
Additional info:
I'm not really sure how relevat this error is or how dangerous it could be.
I'm running classic session on wayland.
You don't happen to run a chromium based browser or application? That warning is from chromium, probably printing it to stderr/stdout thus ending up in gnome-shell's journal stream. There is no `buffer_manager.cc` in mutter or gnome-shell.