EbonJaeger

Thanks, nothing to report in this new Solus update (71 packages, 810,64 MiB).

Just a question:

The GNOME edition will have Software, while all other editions have Discover. Each software center will be automatically installed on already installed systems at a later date.

Having installed Budgie desktop on my computer, I thought I had to use Gnome Software (I have it installed and am currently using it) and that Discover was reserved for Plasma users.
Reading your post, it seems I have to use Discover.
Could you please tell me if I need to correct this?

Thanks for your feedback.

      penny-farthing In reality, you can use whichever you want. What will come installed on Budgie and Xfce editions will be Discover, though, and Discover will probably be added as a dependency of the branding packages or something so that everyone has some software center installed once Solus Software Center goes away.

        The last update for week 11 broke launching certain games for me and I have no idea what the cause might be, but the error persists. It appears to only concern Unity games at the moment (Lutris error log). Steam launches fine, but when I click the "Play" button, unity games just won't launch further, i.e. no pop-up of a game client to log-in or update the client. Different non-Unity offline games I launched from Lutris (also different prefix and different runner) ran just fine.

        Same with games run from Lutris which are started totally different than Steam: runner is wine-ge-8-26 instead of Proton, different prefix, different variables. Disabling dxvk and d3d12 helps with starting, but then graphical blur occurs without a mouse pointer.

        So I reverted to the last history step via sudo eopkg hs -t # right before the update, everything works as expected for the moment.
        Using Budgie LTS Kernel.

        AlphaElwedritsch You are not alone. Reported Bluetooth issues in Plasma Wayland further up in this thread. I wonder if your Bluetooth devices are V4 or above as V3 Bluetooth stuff still seems perfectly functional for me.

            Error preparing initrd: Device error
            start_image () returned Device Error

            This problem with my "NVMe SSD" boot driver is back after this update, even the kernel driver is the same. So it must be something else. Also, my PC freezes directly after update, I had to do hard reset. I have my backup boot partition on another disk (normal SSD) and it works. packages

              AlphaElwedritsch Yes that makes sense. I wonder if we are going to get 5.9 as a fix. Using an older Bluetooth mouse for the time being.

                Maybe I can try testing it later the day or tomorrow.
                One of my mice is a dual device, but I'm actually not sure if it is v5/v4 or v5/v3

                @BuzzPCSOS
                You're right
                I've updated my system again
                My MX Master mouse (v5) stops working immediately
                But the other mouse (dual V5 and V3) which I has connected as a V3 mouse to my system before I did the update keeps working without any problem.

                So, the problems is defacto there, but only for V5 devices

                I will update the issue, I#ve opened on github

                https://github.com/getsolus/packages/issues/5268

                  At home I found an old small bluetooth mouse 'GENIUS' with a large bluetooth antenna, inserted batteries into it and after several manipulations connected it to Solus 4.7 What is curious is that bluetooth does not see the name of the mouse, He does not know its name! I assume it has Bluetooth version 3

                  The mouse works, but on my Acer laptop it is unusual to see a large Bluetooth antenna intended for PC system units

                  @WetGeek as I remember, you have a lot of Bluetooth devices. Have you any problems with your devices since the last sync update?

                  minh
                  Thanks for the heads up, I'm on Budgie with an NVME boot drive & Nvidia gfx card. So I did a test, I installed all updates apart from the x4 Nvidia packages. Rebooted & everything was fine...then I thought I'd 'risk it for a biscuit' & installed the x4 Nvidia packages & it borked to that same recurring error message you have. I didn't have any extra kernels installed, so I had to live usb chroot & rolled backed to before x4 Nvidia packages when all good.
                  So No Visual Interface Display Is Accessible - the way it's meant to be..?

                    Same issue than 2 weeks ago, previous fallback kernel did not remove itself, had to clear it manually for the new one to install correctly. Is editing the EFI partition size safe to do ? 😱

                      BuzzPCSOS Fixed on unstable. Try this. sudo eopkg it https://cdn.getsol.us/repo/unstable/b/bluez/bluez-5.80-58-1-x86_64.eopkg

                          ReillyBrogan Thank you for the swift response. Unfortunately that fix did not work for me. I can still connect Bluetooth V3 devices but V4 devices fail to connect.

                              BuzzPCSOS same for me. I mentioned this already yesterday in the issue on git. Maybe this fix fixes something but unfortunately not everything.