EbonJaeger changed the title to Solus Updates for Week 44, 2024 .

Harvey Using budgie hit shutdown but it didnt popup secondary screen waited and it shut down
other than that appears no issues.
I mean waited seconds not long but slow

    This is why we want offline updates (Both gnome-software and Discover support it).

    If people encounter this as already hinted a hard shutdown / reset is not needed. Just open a terminal and run reboot or halt -p to power off.

      Axios Using budgie hit shutdown but it didnt popup

      Can confirm that, a reboot from terminal was enough. Everything looks good for now 👍

        I didn't realize Hyprland was in the repos. I assume it gets treated like Sway when it comes to support and packaging. I've watched several people's YouTube reviews and demos of it(especially @mylinuxforwork channel), and it looks like a very cool tiling window manager. I tried to play with it on a virtual machine a while back, but Hyprland and VirtualBox didn't get along. I may have to give it another try either in a VM again or on an older laptop.

        nolan budgie, I normally gnome-terminal/rebootand that worked. did not try anything else

        Harvey This is why we want offline updates (Both gnome-software and Discover support it).

        interesting. good.

        One machine done reboot and all came back up, looks ok. Will do main machine after backup finishes.

        Installing egl-gbm, version 1.1.2, release 2
        File conflicts:
        /usr/lib64/libnvidia-egl-gbm.so.1 from nvidia-glx-driver-common gets replaced by egl-gbm package

        Extracting the files of egl-gbm
        Installed egl-gbm
        Installing 95 / 233
        nvidia-glx-driver-common-560.35.03-548-1-x86_64.eopkg [cached]
        Installing nvidia-glx-driver-common, version 560.35.03, release 548
        Upgrading to new distribution release
        Extracting the files of nvidia-glx-driver-common
        Not removing conflicted file : /usr/lib64/libnvidia-egl-gbm.so.1
        Upgraded nvidia-glx-driver-common

        Seeing the above on main machine should I reboot?

          banger Did your updates actually fail or did you just notice that in the output? If the latter then that's normal and happens when a file is moved from one package to another.

            ReillyBrogan

            Yes I just noticed it in the output so its safe to reboot I assume. Nothing to indicate the updates failed.

            One laptop and three of my VMs installed perfectly. The Plasma VM just displayed a black screen, with the mouse cursor only visible in the window's client area. It's bedtime here, I'll fuss with it in the morning, and maybe I'll figure out how to fix it. G'night all!

              Pain free as always. Solus 4.6 is now showing up everywhere. Awesome
              Thanks guys...

              Did all the updates. No errors, but if I boot on the new kernel 6.11 I get a black screen and my monitors do not turn on(No Signal). If I boot to 6.10 all working as normal. I am on Plasma with AMD CPU & 2 AMD GPU's. Is it possible that with the new kernel my default GPU changed? Normally my PC uses the 6700XT and not the 6400.