Closed Bug 734297 Opened 12 years ago Closed 12 years ago

about:support incorrectly says I get no WebGL because I don't have EXT_texture_from_pixmap

Categories

(Toolkit :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 653102

People

(Reporter: zwol, Unassigned)

Details

On my Linux desktop, WebGL is currently blacklisted because the Nouveau driver is buggy (see bug 729817).  However, in trunk, about:support reads

| Adapter Description     nouveau -- Gallium 0.4 on NV94
| Vendor ID               nouveau
| Device ID               Gallium 0.4 on NV94
| Driver Version          2.1 Mesa 7.11.2
| WebGL Renderer          Blocked for your graphics driver version.
|                         Try updating your graphics driver to version
|                         <Anything with EXT_texture_from_pixmap support>
|                         or newer.

The "try updating your graphics driver" message is supposed to read

|                         Try updating your graphics driver to version
|                         <Not the Nouveau driver>

I just wasted nearly an hour trying to figure out why EXT_texture_from_pixmap wasn't being detected successfully, when in fact it _is_, but the message is wrong.

(I don't see any component specifically for about:support)
Known problem: our blacklisting code does some excessive caching of stuff. See bug 653102.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Also, I'm very sorry you wasted nearly an hour because of that.
It wasn't totally wasted; I have a much better understanding of how we probe GL on X now.  I appreciate the sentiment, though.

I'm kinda thinking there should be a way to get the raw glxtest report dumped to stderr -- that would have saved some effort.
I'd accept a patch doing that (probably commanded by an environment variable). But note that glxtest currently redirects its stderr /dev/null to avoid polluting firefox's stderr output, so you would have to change that too when that env var is defined.
You need to log in before you can comment on or make changes to this bug.