Bug 1728220

Summary: ERROR:buffer_manager.cc
Product: Red Hat Enterprise Linux 8 Reporter: Tomas Pelka <tpelka>
Component: mutterAssignee: Jonas Ådahl <jadahl>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: fmuellner, jkoten
Target Milestone: rc   
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 15:46:20 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:    
Bug Blocks: 1678350    
Attachments:
Description Flags
journal.log none

Description Tomas Pelka 2019-07-09 11:06:40 UTC 
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.
Comment 1 Tomas Pelka 2019-07-09 11:08:15 UTC 
Created attachment 1588687 [details]
journal.log
Comment 2 Jonas Ådahl 2019-07-09 12:47:21 UTC 
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.
Comment 3 Tomas Pelka 2019-07-09 14:31:04 UTC 
yes I do run google-chrome and franz which is chromuim based too, so probably close as wontfix