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.

                  AlphaElwedritsch it's fastfetch with a config file to make it look like this. I found it online and made a few small changes. Let me know if you want the config file.

                      Update went smoothly but there is a bug now on Libreoffice: field shadings doesn't appear anymore, even when it's on. Is there any way to fix this?

                        Also noticed that little bug in the Firefox search bar. The line stays at the beginning of the word instead of the opposite.

                        EDIT : Seems like it's solved after a second reboot.

                        WetGeek The Plasma VM just displayed a black screen, with the mouse cursor only visible in the window's client area.

                        I was really tired at the time, and what I was trying to say was that the mouse cursor was NOT visible in the window's client area. I could click in the system area - such as to close the window - but could do nothing with the Plasma client.

                        This morning it occurred to me that things didn't go black until after I'd logged on, so I thought I'd try an X11 session instead of my default of Wayland. Indeed, that worked. I was able to start a session and install the 203 upgrades, but after a reboot, a Wayland session was no longer avaliable as an option. Just X11.

                        Since I'd updated the host machine (my laptop) first, I was obviously using the upgraded VirtualBox to run these VMs, and since there's been no problem with my laptop (also using Wayland), my initial assumption is that the root cause of these troubles is with the upgraded VirtualBox system on the laptop. Why it should affect just the Plasma VM I don't know. Perhaps that's the only VM that uses Wayland at this point? I'm not sure.

                        I shouldn't need to do this, but out of curiosity I'm going to install the guest additions to see whether that has any effect on that VM. Beyond that, I'm out of ideas. It's not a tragedy for this one VM to use X11 until things get fixed, so I can wait patiently to see whether it works better after the next VirtualBox upgrade.