I had to get rid of Clapper it stopped opening videos with this update
Never used much so I just deleted it.
Other than my brave keyring issue eveything seems alright so far tested alot last nite could not sleep...lol
(Oh no missed another one Burnfix (Flatpak) does not run at all.)
My other flatpaks seem alright so far
Ok did (Flatpak update) its working now.
Clapper is still not working (Uses gnome 43)

(Will leave this here if others need.)

It would be helpful if people experiencing issues with flatpaks could open an issue for it. Please include which flatpaks are having issues. Hopefully it's something we can fix without having to downgrade package versions.

    ReillyBrogan It's not anything new.

    Ah ... just new to me, then -- I'd never seen it before. Thanks for your reply.

      Axios except brave asking for keyring

      Brave has been asking for password here (my Solus Budgie) too for a while now. I was told on this forum that this is Gnome stuff, and we can do nothing about it. Small potatos..... no problem.

          webkitgtk 2.42.3 cherry-picked to fix some security vulnerabilities. See here for vulnerability details, here for the release notes for v2.42.3.

            86 packages, reboot, kicked the tires, kopasetic 👍️ . thank you.

            PS--no one wants a haggis taco. No one.

            ReillyBrogan just got 'em and installed them.

            "Impact: Processing web content may disclose sensitive information. Apple is aware of a report that this issue may have been actively exploited. Description: An out-of-bounds read was addressed with improved input validation.
            "Impact: Processing web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited. Description: A memory corruption vulnerability was addressed with improved locking.

            serious business, thanks for getting on it.

              Axios Thanks but I will not do any of that 'convoluted' stuff. I really don't mind entering my password.
              😄

                  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?