Hello. I got the following errors:

Installing 70 / 100
mesalib-devel-20.0.7-140-1-x86_64.eopkg [cached]
Installing mesalib-devel, version 20.0.7, release 140
Upgrading to new upstream version
Extracting the files of mesalib-devel
Not removing conflicted file : /usr/include/EGL/egl.h
Not removing conflicted file : /usr/include/EGL/eglext.h
Not removing conflicted file : /usr/include/EGL/eglplatform.h
Not removing conflicted file : /usr/include/GL/gl.h
Not removing conflicted file : /usr/include/GL/glcorearb.h
Not removing conflicted file : /usr/include/GL/glext.h
Not removing conflicted file : /usr/include/GL/glx.h
Not removing conflicted file : /usr/include/GL/glxext.h
Not removing conflicted file : /usr/include/GLES/egl.h
Not removing conflicted file : /usr/include/GLES/gl.h
Not removing conflicted file : /usr/include/GLES/glext.h
Not removing conflicted file : /usr/include/GLES/glplatform.h
Not removing conflicted file : /usr/include/GLES2/gl2.h
Not removing conflicted file : /usr/include/GLES2/gl2ext.h
Not removing conflicted file : /usr/include/GLES2/gl2platform.h
Not removing conflicted file : /usr/include/GLES3/gl3.h
Not removing conflicted file : /usr/include/GLES3/gl31.h
Not removing conflicted file : /usr/include/GLES3/gl32.h
Not removing conflicted file : /usr/include/GLES3/gl3ext.h
Not removing conflicted file : /usr/include/GLES3/gl3platform.h
Not removing conflicted file : /usr/include/KHR/khrplatform.h
Not removing conflicted file : /usr/lib64/pkgconfig/egl.pc
Not removing conflicted file : /usr/lib64/pkgconfig/gl.pc
Not removing conflicted file : /usr/lib64/pkgconfig/glesv1_cm.pc
Not removing conflicted file : /usr/lib64/pkgconfig/glesv2.pc
Upgraded mesalib-devel
Anything to worry about? Thanks! :-)

    Updating my laptop (Budgie), there were no indications of a problem, but after rebooting, I could no longer use my GUI. The computer starts normally, displaying the logon screen, then the monitor clears, and as it normally does, starts by displaying an empty bottom panel. But before anything populates the panel, the screen goes totally black and stays that way.

    I can start a tty, and a check of the installation showed that nfs-utils was broken, so I fixed that by fetching that one file with eopkg it nfs-utils --reinstall and rebooted, but that made no apparent difference. I'm going to try doing a restore (for the first time) using restic, but I'll wait a while to find out if anyone else has a better solution. I'm sure that most of the upgrades were fine, and there may be a more targeted way to solve this

    My MATE computer that runs the TV installed far fewer updates, and it had no issues at all. Holding off on updating the rest of our Budgie computers for now.

      WetGeek
      Make sure you did a full upgrade: sudo eopkg up -y

      An please provide the output of uname -r

          Harvey An please provide the output of uname -r

          Yes, I used the same script that I always use, and has never failed. It starts out with eopkg up -y.

          5.6.18-155.current

              I have updated without any issues. Thanks for all the hard work that was put into the mesa build! <3

              WetGeek
              Ok then I can only suggest creating another thread to help make sure your post gets seen, as it is not related to the OP's question.

                Just a follow-up: A regression in VirtualBox crept back in and it appears to be what is causing the issue. @DataDrake is removing that applicable code from VirtualBox and will be pushing the update to stable as soon as possible. Thank you all for being so quick to report the issue and provide information that helped us narrow it down (including all the folks in IRC). You're all amazing ❤️

                Fix deployed to stable. If you come across this issue, please just run sudo eopkg up after logging in to a TTY. This can be accessed using Ctrl+Alt+F1-F7 (pick one, shouldn't matter unless you hit the graphical TTY).

                If you are unsure if you're affected, double check for virtualbox-guest-common after doing an upgrade. You can check if you have it installed by running sudo eopkg info virtualbox-guest-common. If you have it installed, it'll say.

                If you have it installed and it is 6.1.10-159 then you should be fine and no intervention should be necessary (you can safely reboot). If you don't have that version and you haven't rebooted yet, just check for updates again and you should see some virtualbox ones. If you don't have any virtualbox guest driver bits installed, you should be able to safely ignore all the things and reboot as usual.

                If you have no need for anything related to virtualbox, you can remove virtualbox-guest-common as well!

                If you have any further issues related to booting / reaching the graphical session after getting all your updates, please report it so we can take a look as soon as possible. Thanks!

                Well. It was the same update as usual. Extremely boring. Everything works great, as usual, as usual. as usual. Solus is the most boring OS there is. I hate it. 😁 😁 😁 .