totaluf.blogg.se

Font explorer x bug signal 11
Font explorer x bug signal 11






font explorer x bug signal 11

WEBGL1 is not automatically activated (also not by clearing cache), but the I do not quite understand how things are supposed to work now, but Still is present, but does not harm, and possibly to typical properties The warning "More than 1 GPU detected via PCI, cannot deduce vendor" The error "glxtest: libGLESv2 glGetString returned null" indeed has

font explorer x bug signal 11 font explorer x bug signal 11

I tested nightly at Debian Bullseye (32 bit). Now while this definitely should get fixed in mesa so setups like this have a chance of getting WebGL 1 support, what needs further investigation is why things fall apart - I assume some process crashes or so. Your about:support indicates that this works fine.įor the record: this probably have started after bug 1640053 landed, which makes us use EGL in glxtest instead of GLX. However, that should not make the whole browser break - it should simply fall back to software rendering. The GLX version, however, works just fine. I pocked at this a bit and got some weird result.įirst of all I using MESA_GLES_VERSION_OVERRIDE=2.0 with the EGL version of glGetString makes it break - it always returns NULL, making us fail with the above message. Jan 29 16:51:29 debian kernel: : Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. This can be caused by duplicate bus devices for same VGA controller, which seems to be a known property of 945GM:Ġ0:02.0 VGA compatible controller : Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)Ġ0:02.1 Display controller : Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) : More than 1 GPU detected via PCI, cannot deduce vendor In that case at Nightly with wayland and without wayland still remain the same errormessages: This error disappears if LIBGL_ALWAYS_SOFTWARE=1 is used.Īfter clearing the cache WEBGL1 and WEBGL2 are supported again according to "about:support", but firefox with wayland still is not usable. This is strange because Wayland itself supports ES 2.0 and firefox previously did not give problems with ES 2.0. Glxtest: libGLESv2 glGetString returned null Looking at the source I have the impression that Beta and Nightly now require a minimal version ES 3.0. Intel Open Source Technology Center - Mesa DRI Intel(R) 945GM x86/MMX/SSE2 At previous versions, Firefox with Wayland accepted OpenGL ES 2.0:








Font explorer x bug signal 11