latest mesa breaks wayland – workaround

HI/2 all…

The latest mesa code reverted to using the wayland libwayland-egl, instead of using their own, so if you are having this error:

error while loading shared
libraries: libwayland-egl.so.1: cannot open shared object file: No such
file or directory

install the following package:

apt install libwayland-egl1

this should fix things for now, mesa is in flux right now with this new change.

sorry for the inconvenience.

Leave a Reply

Your email address will not be published. Required fields are marked *

8 responses to “latest mesa breaks wayland – workaround”

  1. foo Avatar
    foo

    Big thanks for your efforts. An annoying little bit this. It actually broke almost everything for me on bionic.
    Think we’ll have to revert back again at some point?

    1. Paulo Dias Avatar
      Paulo Dias

      No need, it is fixed now (should be with latest build), we will be using the native wayland, instead of the old mesa one.

      enjoy.

      1. Gabriel Avatar
        Gabriel

        Hi there Paulo!

        Clean Kubuntu 18.04 installation here. Just added your Unstable PPA and still got the error after rebooting (while trying to open Firefox). I installed `libwayland-egl1` and fixed it but wasn’t this suposed to be fixed already?

        Thank you very much!

        Abraços,
        Gabriel

        1. Paulo Dias Avatar
          Paulo Dias

          Hi gabriel, can you test a clean install again?

          it should be pulled correctly now, when you install the main mesa libs.

          regards

          1. Gabriel Avatar
            Gabriel

            I’ll try as soon as I come back from work!

            Thank you very much!

          2. Gabriel Avatar
            Gabriel

            `XPCOMGlueLoad error for file /usr/lib/firefox/libmozgtk.so:
            libwayland-egl.so.1: cannot open shared object file: No such file or directory
            Couldn’t load XPCOM.`

            purged the ppa, removed libwayland-egl1, rebooted the machine and installed your drivers again but…

            odd, isn’t it?

  2. Karry Hane Avatar
    Karry Hane

    @Paulo Dias

    Is it really fixed? Because I just got this on Ubuntu 18.04 after installing Padokas Unstable drivers.

    1. Paulo Dias Avatar
      Paulo Dias

      Hi karry, can you test a clean install again?

      it should be pulled correctly now, when you install the main mesa libs.

      regards