Bug 333372 - Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=*)
Summary: Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=*)
Status: RESOLVED WORKSFORME
Alias: None
Product: kinfocenter
Classification: Applications
Component: OpenGL (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: David Hubner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-13 11:33 UTC by Elias Probst
Modified: 2020-02-16 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
glxinfo output (16.57 KB, application/octet-stream)
2014-04-13 11:36 UTC, Elias Probst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2014-04-13 11:33:56 UTC
Running kinfocenter from KF5-based git master (05a4af6c0768be5a40ab965b124336b68ad08022).
Using the OpenGL module results in a lot messages like this one on the terminal:

Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_QUERY_COUNTER_BITS)

Suspected EGL/GLES support first to cause this, but even when building kinfocenter only with OpenGL and without EGL and/or GLES this still happens.

Although the information in the OpenGL module seem to be displayed correctly, this points towards a possible issue.
Comment 1 Elias Probst 2014-04-13 11:36:20 UTC
Created attachment 86067 [details]
glxinfo output

Probably some relevant information… attached the full output of 'glxinfo'.

Short excerpt with the most important information:
OpenGL version string: 3.0 Mesa 10.0.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
Comment 2 Andrew Crouthamel 2018-11-11 04:23:23 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:29:41 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Harald Sitter 2020-01-17 15:28:56 UTC
Still needs re-testing.
Comment 5 Bug Janitor Service 2020-02-01 04:33:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2020-02-16 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!