| Summary: | libGL warning: 3D driver claims to not support visual 0x51 | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Diego <diego> |
| Component: | GLX | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | high | CC: | amlau, compnerd, daniel.hornung, krzysiek.pawlik, pip, russ, sebastian, sndirsch, svu, sylecn |
| Version: | git | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
disable-libGL-warning.diff
patch for filtering warnings about non-conformant visuals |
||
|
Description
Diego
2006-04-21 21:58:37 UTC
*** This bug has been marked as a duplicate of 6624 *** Reopening for the client side warning. It's caused by the visual being marked non-conformant by AIGLX. A solution is being discussed on the mesa3d-dev mailing list. Note that this is completely cosmetic and has no functional impact. *** Bug 10612 has been marked as a duplicate of this bug. *** Since I still see this issue with Mesa 7.0. Anyone who can at least give me a pointer to the mentioned discussion on mesa-dev? I couldn't find it. :-( (In reply to comment #4) > Anyone who can at least give me a pointer to the mentioned discussion on > mesa-dev? I couldn't find it. :-( I'm not sure, but I think I was referring to http://www.mail-archive.com/mesa3d-dev@lists.sourceforge.net/msg01301.html . Some experiments of mine indicate the caveat isn't the only problem though. Another approach might be to add an entry corresponding to the AIGLX visual on the client side, either in each driver or libGL itself. Thanks, Michael. Strangely I get this message even when AIGLX is disabled. > Another approach might be to add an entry corresponding to the AIGLX visual
> on the client side, either in each driver or libGL itself.
Any ideas where thes are defined in Mesa sources?
Created attachment 11107 [details] [review] disable-libGL-warning.diff braindead patch (In reply to comment #8) > Created an attachment (id=11107) [details] > disable-libGL-warning.diff > > braindead patch Hmm. I don't think the id as such has any inherent meaning (so it could potentially change), I think though it's always the last mode. Maybe it would be better to filter the GLX_NON_CONFORMANT_CONFIG bit in the VisualRating instead, I don't think those are used anywhere else (and even if they were it would only suppress the warning if the driver can't support it anyway). Thanks for the proposal. Unfortunately I can't say. I have exactly no idea of Mesa sources. Maybe you can provide an appropriate patch? Created attachment 11112 [details] [review] patch for filtering warnings about non-conformant visuals What about this patch instead. Just filters warnings about unsupported non-conformant visuals instead of relying on the visual id. Not sure though it's a good solution neither... Thanks. This is definitely a better patch. Hmm. Shouldn't it be
if (m->visualRating != GLX_NON_CONFORMANT_CONFIG)
^^
?
(In reply to comment #13) > Hmm. Shouldn't it be > > if (m->visualRating != GLX_NON_CONFORMANT_CONFIG) > ^^ Oops. Yes of course... Can you commit the patch into git and/or discuss it with Brian Paul? I'm afraid otherwise this issue will never get fixed upstream. :-( The warning is *very* confusing for users ... I've been tempted to simply disable the warning for quite a while. It's annoying and misleading. I think Ian's the only person that knows the whole story behind it. *** Bug 6624 has been marked as a duplicate of this bug. *** Roland pushed his patch to Mesa GIT. Thanks a lot! my video card is a 865g intel my linux distro is slackware 12 Mass version move, cvs -> git |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.