(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
>
> iris
> ----
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported modifier, resource creation failed.
> XXX: resource creation failed
>
> zink
> ----
> $ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
>
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
>
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Zink will use internally lower-level parts from the Iris driver to access
the hardware, so at least this indicates that the issue is *below* the
OpenGL/GLES implementation. Could be EGL or hardware access, I suppose.
> i965
> ----
> $ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
>
> WaylandCompositor requires eglBindWaylandDisplayWL,
> eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer.
> Nested Wayland compositor could not initialize EGL
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
When a driver that was set explicitly like this fails to load, Mesa falls
back to using software rendering. This means you ended up here using the
swrast/llvmpipe driver, most likely (you can load “webkit://gpu” in the
Minibrowser or Epiphany to check this). This means that WebKit is most
likely using the GLX/EGL/OpenGL/GLES APIs correctly and the issue lies
somewhere in the Intel driver.
But the version of Mesa I am using here is the same as you and it works.
My suspicion is that one of the following is happening:
* Patches applied by Debian/Ubuntu on top of Mesa are breaking the Intel
driver. Here I am using Arch Linux, which does not apply any patches.
* The Intel driver is being miscompiled somehow by the compiler toolchain
shipped by Ubuntu. In case it helps, here Arch stable has GCC 11.2.0 as
the default system compiler, so that's what gets used to build packages.
* The bug could be related to your particular GPU model (and the
corresponding code inside Mesa for it).
I hope this helps :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1966418
Title:
[jammy regression] Evolution does not display message content anymore
Status in Mesa:
Unknown
Status in Webkit:
Confirmed
Status in epiphany-browser package in Ubuntu:
Invalid
Status in evolution package in Ubuntu:
Invalid
Status in gnome-control-center package in Ubuntu:
Invalid
Status in liferea package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Confirmed
Status in webkit2gtk package in Ubuntu:
Confirmed
Bug description:
Impact
------
All webkit using apps for affected users display a blank screen.
Original Bug Report
-------------------
Evolution has suddenly stopped displaying message contents on the last 24h.
Starting it up from the command line shows this output:
```
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
```
I don't know if it's related, but googling around shows some webkitgtk
hits on this error.
The email contents are however clickable. They're just not rendered to
screen (see attached file).
Deleting the evolution folders from `~/.config`, `~/.cache` and
`~/.local/share` does not help.
Email accounts are all google, configured through gnome online
accounts.
Workaround #1
-------------
You can run the app from the command line with
WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
(Replace evolution with the name of the webkit app you are trying to use)
Workaround #2
-------------
Log out.
Select your name on the login screen.
Click the gear button and choose Ubuntu on Xorg.
Enter your password to finish logging in.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evolution 3.44.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Fri Mar 25 10:55:49 2022
SourcePackage: evolution
UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966418/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
