For my part, I have processed 2 updates today (this morning, 117 packages (1.35 GIB) and this evening 3 packages (67.33 MIB)) without encountering any particular problem after rebooting.

When you read the detailed report written by @ReillyBrogan concerning updates made this week, it is incredible to see again the fantastic work carried out by the Solus team of developers.

This deserves cheers. 👏

elfprince Ahh np I just did it and worked ok that webpage appears to complicated and its not
to people. I only have that problem with brave for some reason.

    Since this update Nemo has decided that my bookmarks pointing to (already mounted) external drives are not good anymore. I need to navigate manually once, then it will decide that the bookmarks can be actually used.

    The error it gives is

    Could not display "/bookmarked/path"
Nemo cannot handle "file" locations

    Hi all,
    I have a small issue after this update. Protonmail-bridge does not start and I got the following message :
    Cannot connect to Go backend via gRPC: Connection to the gRPC server failed because of a timeout
    And until that message appears, I have my panel blocked. Should I filed a bug or is it something that could be
    sorted easily ?

    This update resulted in my Budgie desktop environment being unusable. Raven, panels, and applets would not respond to keyboard shortcuts or mouse interactions. After a few minutes, Budgie would respond normally. This issue persisted after restarts. I was still able to interact with desktop icons and Nemo. I attempted to rollback updates using eopkg, yielding no improved response. I narrowed down the cause of my issue to the ProtonMail Bridge client. After uninstalling protonmail-bridge from the software center, my system is working as it should.

    Running Solus on an NVMe drive in an SSD enclosure connected via USB to a Lenovo Legion laptop. Everything's been fine with the setup for several months.

    The update completed with no errors. But on restart, it gives a black screen.

    I went through the steps at https://help.getsol.us/docs/user/troubleshooting/boot-rescue/, including rolling back to the prior transaction, but the issue persisted.

    I thought, ok, I will just nuke and start over, as this system doesn't have much on it. It's not the one I use primarily. So, installed. Fine. Run updates. Restart. And … black screen.

    What can I do?

      david if you tap the down key while booting it should display the boot menu. Does it work if you boot into the previous kernel? You may need to do it a few times as the window to activate the boot menu is fairly short.

          ReillyBrogan Perfect, thank you! I'd heard of this option but hadn't had to (or known how to) use it before.

          The 6.6 option gives the black screen. The 6.5 brings to log-in screen but keyboard and mouse don't work.

          The 6.3 option works just fine. 👍️

              david I imagine that you just re-used your existing boot partition when you reinstalled your system which is why the 6.5 kernel is present. Unfortunately the matching kernel modules folder isn't present on your reinstalled system which is why it's not able to load the driver for your keyboard and mouse (probably the driver for the USB ports they're plugged into). You can just ignore that particular boot entry since it's not going to be useful to you and will be cleaned up anyway.

              Boot failures are obviously not desirable to us and we'd like to get this fixed so you don't have to keep booting into an older kernel indefinitely. Would you mind creating an issue on our bug tracker? We'll walk you through collecting diagnostics information as needed and likely provide test kernels that you can install to help us narrow down the issue.

                  Even tho I updated when I posted earlier did it again and I would say it helped again.
                  I have about 6 flatpaks all work. (graphics and speed are better)
                  Tried Clapper flatpak again its a no go (Guess they got issues with there flatpak)

                  Thanks for letting us know again.

                  The clapper flatpak appears to be using the GNOME 43 runtime which is end of life and no longer being updated. You should open an issue with the clapper project and let them know that flatpaks using the GNOME 43 runtime will no longer run on systems that use Mesa 23.3. The solution is to move to a newer runtime.