From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103371] glxinfo -l shows GL_INVALID_ENUM
Date: Thu, 22 Feb 2018 13:49:51 +0000 [thread overview]
Message-ID: <bug-103371-502-RJIzxrZRMh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103371-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 673 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103371
Marc Dietrich <marvin24@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTABUG
--- Comment #5 from Marc Dietrich <marvin24@gmx.de> ---
ok, seems to be a false alarm. The (likely) valid error is only produces in
debug builds (either meson or autotools). maybe glxinfo should not ask for
these limits in compat context.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2122 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-22 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:34 [Bug 103371] glxinfo -l shows GL_INVALID_ENUM bugzilla-daemon
2018-02-22 10:35 ` bugzilla-daemon
2018-02-22 10:45 ` bugzilla-daemon
2018-02-22 10:54 ` bugzilla-daemon
2018-02-22 12:46 ` bugzilla-daemon
2018-02-22 13:49 ` bugzilla-daemon [this message]
2018-02-22 14:36 ` bugzilla-daemon
2018-02-23 9:20 ` bugzilla-daemon
2019-09-18 19:24 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-103371-502-RJIzxrZRMh@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.