Forum Discussion

josh_bodner's avatar
josh_bodner
Former Employee
Mar 23, 2021

Dev channel update to 91.0.831.1 is live

Hello Insiders!  Today we’re releasing build 91.0.831.1 to the Dev channel.  To start out, we’ve got two big features we’re excited to unveil, as well as some other exciting community updates:    ...
ZiZouJH's avatar
ZiZouJH
Copper Contributor
Mar 25, 2021

Unfortunately, on the Linux version, Edge is now bound to glibc v2.18 instead of glibc v2.17.

 

As a result, it is not possible to install Microsoft Edge v91.0.831.1 anymore on CentOS 7, Red Hat Enterprise Linux 7 and others (Oracle, etc) that are built on glibc v2.17.

This is what yum returns when trying to update Edge (in French but you will understand):

---> Le paquet microsoft-edge-dev.x86_64 0:91.0.825.0-1 sera mis à jour
---> Le paquet microsoft-edge-dev.x86_64 0:91.0.831.1-1 sera utilisé
--> Traitement de la dépendance : libc.so.6(GLIBC_2.18)(64bit) pour le paquet : microsoft-edge-dev-91.0.831.1-1.x86_64
--> Résolution des dépendances terminée
Erreur : Paquet : microsoft-edge-dev-91.0.831.1-1.x86_64 (microsoft-edge-dev)
Requiert : libc.so.6(GLIBC_2.18)(64bit)

 

Would you plan to attach to version 2.17 back again or is it necessary to keep binding to version 2.18 for new features?

  • lorne_mitchell's avatar
    lorne_mitchell
    Former Employee
    Apr 02, 2021
    Thanks for reporting on this! We're working on a fix.
    • ZiZouJH's avatar
      ZiZouJH
      Copper Contributor
      Apr 15, 2021
      Many thanks for the fix 🙂
      I will continue to use an up-to-date Edge on my CentOS 7 and many people will still be able to do it!
      • ZiZouJH's avatar
        ZiZouJH
        Copper Contributor
        Apr 15, 2021

        josh_bodner actually I still have the issue in build 91.0.852.0-1. I guess the fix will be included in the next build?

  • unmention's avatar
    unmention
    Copper Contributor
    Mar 25, 2021

    I got the same error.

    I only use edge for testing so it is annoying but not critical. I know that Redhat 7 and it's derivatives are considered old and if dropping glibc 2.17 is MS's decision then so be it. We will just send the Edge testing further downstream where Windows desktops dominate.

    • ZiZouJH's avatar
      ZiZouJH
      Copper Contributor
      Apr 01, 2021
      If there is a reason for this, that is to say any feature that needs glibc v2.18+ and cannot be built with an older version, I would say OK, I understand.

      However, that is a huge compatibility break. Even if they are quite old, the Red Hat Enterprise Linux 7-like distributions are not that obsolete and they still have official updates as far as I know. What is certain is that no more Edge support on this Linux branch removes a lot of universality for this browser.

      Was this considered?
      • unmention's avatar
        unmention
        Copper Contributor
        Apr 11, 2021
        I can only speculate as to why MS dropped support for glibc <2.18. It may be there is a feature in 2.18+ that is necessary. However, considering that Chromium -- which underlays Edge -- still runs fine on the older platforms I am a little skeptical of that.

        In any case, this is not a new phenomenon. I saw similar behavior from Google and Mozilla as Redhat 6 approached it's end-of-life and it makes a certain sense: At the core, Linux is a server OS and a browser is not really necessary on a server. The market for any graphical browser on Linux right now is only a small percentage of the total of Linux installations.

        I guess I now have to worry if they will similarly break teams... 🙂

Resources