Failed to create EGLContext!: 0x3005
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: w.pelser, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
I tried to enable WEBRender on my machine
Actual results:
I always get the error message in about:support mentioned above.
Expected results:
full wayland with
openSUSE TW,
plasma 5.18.3/5.68.0, qt 5.14.1, graphic is intel G45 onboard
should be able to run webrender
I wanted to attach the contents of about:support as a text-file, but on full-wayland it seems not to be copied into the clipboard.
I followed Martin Stransky´s blog "webgl and fgx acceleration on wayland", but without success.
Maybe this graca is too old? But this comment is no longer seen on Firefox 75.
|
||
Comment 2•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
(In reply to W.Pelser from comment #1)
Created attachment 9137685 [details]
contents of about:support as text-file copied from the siteMaybe this graca is too old? But this comment is no longer seen on Firefox 75.
This attachment is obsolete
|
||
Comment 5•6 years ago
•
|
||
gfx.webrender.all true
is enough for WebRender in general. These are not needed for WebRender:
gfx.webrender.compositor true
gfx.webrender.enabled true
layers.acceleration.force-enabled true
layers.gpu-process.force-enabled true
Maybe this graca is too old?
Yes, unfortunately. Intel G45 supports only OpenGL 2.0, but WebRender needs OpenGL 3.2.
https://www.intel.com/assets/pdf/prodbrief/319946.pdf
With optimized performance and support for [...] OpenGL 2.0
You can choose between:
- previous OpenGL compositing (deprecated): layers.acceleration.force-enabled:true (reset other prefs to their default = disable WebRender)
- Software rendering (default)
Thank you for your immediate and detailed answer. This helped me, to learn, not to mix up opengl and webrender in about:config. And gave firefox the optical stability, I was looking for.
My graca (X4500HD) supports opengl 2.1. which may be an important difference sometimes.
The confusing thing is, that webrender with this graca seems to be possible on windows, but not on linux. I have read somewhere that such old gracas will work with webrender sometimes in the future. Maybe waiting could be an option.
|
|
||
Comment 7•6 years ago
|
||
GLES 2 support seems a bit unclear, but is tracked with bug 1541975. To address such cases and to circumvent driver bugs, they're working on a performant software GL backend for WebRender as fallback solution that works everywhere (bug 1601053).
Keep an eye on https://mozillagfx.wordpress.com and https://twitter.com/FirefoxNightly. Thanks!
(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #5)
gfx.webrender.all true
is enough for WebRender in general. These are not needed for WebRender:
gfx.webrender.compositor true
gfx.webrender.enabled true
layers.acceleration.force-enabled true
layers.gpu-process.force-enabled true
Maybe this graca is too old?
Yes, unfortunately. Intel G45 supports only OpenGL 2.0, but WebRender needs OpenGL 3.2.
https://www.intel.com/assets/pdf/prodbrief/319946.pdfWith optimized performance and support for [...] OpenGL 2.0
You can choose between:
- previous OpenGL compositing (deprecated): layers.acceleration.force-enabled:true (reset other prefs to their default = disable WebRender)
- Software rendering (default)
Software rendering is not able to make firefox working properly. Ihave to enable "layers.acceleration.force-enable", otherwise the GUI is not reaction visible on input and to work around this bug, I have to switch between open tabs, to make an input visible and working. So in reality there is no choice and Ihave to work with a deprecated setting.
|
|
||
Comment 9•6 years ago
|
||
Software rendering is not able to make firefox working properly. I have to enable "layers.acceleration.force-enable", otherwise the GUI is not reaction visible on input and to work around this bug, I have to switch between open tabs, to make an input visible and working. So in reality there is no choice and Ihave to work with a deprecated setting.
Window-Protokoll wayland/drm
bug 1625296 merged recently. You could try it out with https://nightly.mozilla.org/. Start it with env var MOZ_ENABLE_WAYLAND=1 (or GDK_BACKEND=wayland) as well. Other Wayland bugs are tracked with bug 635134.
Desktop-Umgebung kde
KDE Wayland bugs are tracked with bug 1609115. Your observation sounds like bug 1584845.
It was barely usable for me, so I switched back to XWayland. Upstream fixes are on their way (e.g. bug 1593478 comment 6).
|
Reporter | |
Comment 10•6 years ago
|
||
thank you again for your detailed answer
I have an additional question:
On my screen: firefox in the background breaks the window in the foreground for the first 3 seconds, sometimes longer. There are parts of the backgroundwindow (firefox or thunderbird) visible in the foreground window as dolphin or Kate or others. Is this a firefox bug or a wayland-plasma kde bug? Where sholud I file this -with a better descripton of course-, or is it still an actuall bug, which I could not find until now?
Description
•