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.

      WetGeek I'm going to install the guest additions to see whether that has any effect on that VM

      No, the guest additions failed to install. Things started out OK, but after I provided my authorization, it went on to display an error I'd never seen before, and which didn't hang around long enough for a screencap. And after a reboot, there was once again just the X11 option available for a session.

      I'm moving on to Plan B now - I'll just quit fussing with this until after another VirtualBox upgrade. Surely it will come to the attention of someone at KDE or Oracle who can fix it.

        To elaborate a bit on:
        Firefox has been updated to 132.0. The full release notes can be found here. In addition, GNOME search integration has been added.

        If you are a GNOME user and you are running Firefox, you can now switch to open tabs and open bookmarks and pages from your history via the search in GNOME overview. Open tabs start with (*) in search results.
        This is a really nice feature that integrates Firefox flawlessly into the GNOME shell.

        If you dislike this feature, you can disable it on the search tab in GNOME settings:

        Also, don't forget to check out the nice accent colors introduced in GNOME 47 (appearance tab in GNOME settings).

        Yannnd Same issue. Worked correctly after shutting down and restarting the computer. I'm on Budgie.

          budgie and power:
          manual mouse-click shutdown and reboot work fine both days.
          did not try sudo shutdown because I never use that command.

          Gwen we updated to the newest libreoffice, so it's probably an upstream issue. I'd recommend searching on their bugzilla to see if you can find anything that looks like the same issue, or create steps to reproduce the issue so that we can reproduce it ourselves.

          • Gwen replied to this.

              Oh, we forgot to mention that the fbdev feature has been enabled in the Nvidia driver (nvidia-glx-driver and nvidia-beta-driver). This enables the driver to properly handle TTY rendering which means that switching to an alternate TTY (CTRL + ALT + F3 and similar) should now work properly and look like it does on other desktops. An additional benefit of this is that the unlock screen for full disk encryption should now look much better.

              3 upgrades carried out
              On my main computer Solus_KDE remotely with SSH sudo eopkg up went very well.
              On my Solus_KDE laptop with Discover, no problem.
              On my surface pro 2 tablet Solus_GNOME with the graphical Solus package manager, no problem.
              I'd like to point out that on the 2 graphics upgrades, I disabled standby during installation.

              Hello,
              sorry, have to write with the Google translator.
              This morning I installed SolusOS, after the installation I installed all the updates and restarted it, then I installed the NIVIDIA driver via Solus from the system.
              I couldn't restart gin, had to do a hard reset, then the laptop booted up but I couldn't start any programs, all with Gnome.
              I then tried with KDE, the same process but after the reboot there was a white screen with the comment "an error has occurred"

              HP Omen 17" AMD Rysen 7 8845HS GeForce RTX 4060 (8 GB), 16 GB-RAM

              Hallo,
              sorry muß mit dem Googel Übersetzer schreiben.
              Ich habe heute morgen SolusOS installiert, nach der Installation dann alle Updates eingespielt und neu gestartet, dann habe ich über Solus den NIVIDIA.Treiber installiert also aus dem System.
              Neustart gin nicht, mußte Hartreset durchführen, danach ist das Laptopzwar hoch gefahren jedoch konnte ich kein Program mehr starten, das alles mit Gnome.
              Habs dann mit KDE versucht, der gleiche Vorgang aber es kamm nach dem Reboot ein weisser Bildschirm mit der Bemerkung "ein Fehler ist aufgetreten"

              The wheel of my Logitech wireless mouse started to act up after the upgrade to kernel 6.11. Scrolling was mostly not recognized at all, only sometimes, and then only for maybe half a second, after which it dropped out again. I had had this problem off and on again in the past and was never able to find the root cause, only today I thought of the kernel maybe being the culprit. And, well, it was, I booted into kernel 6.10 and the mouse wheel worked again flawlessly.

              On Gnome does installing a flatpak still break the GUI?

              When I processed the big Solus update yesterday (199 packages, 2.03 GiB), I had to go through the terminal to force a reboot. Afterwards, everything seems to be back to normal, except that the reboots I have to do since display sometimes a more or less streaked white screen that lasts a short time, but then you can log in normally.

              I should point out that I am using Budgie desktop.

              But I discover that I am stuck at linux-current 6.10.11-303 since 2024/09/22, although the subsequent Solus updates have been running successfully.
              So I rebooted my computer and after pressing ctr+space several times, I could see 3 kernels, 6.11.5-307, then 6.10.11-304 and finally 6.10.11-303 with an arrow pointing in front of it.
              So I selected the most recent kernel, then after opening an administrator session, I typed the terminal command:
              sudo clr-boot-manager update
              to keep it.
              Will I have to do these things again with the next kernel update?

              Also, the Solus update report indicates that Thunderbird has moved to version 128.3.3-205, but the application says that it is in version 128.4 esr (64 bits), is this normal?

              Thanks in advance for your feedback.

                penny-farthing Will I have to do these things again with the next kernel update?

                It shouldn't have been required in the first place but apparently it was. Unless you had booted into an old kernel on purpose prior I don't know why this happened nor have I heard of this happening before.

                penny-farthing Also, the Solus update report indicates that Thunderbird has moved to version 128.3.3-205, but the application says that it is in version 128.4 esr (64 bits), is this normal?

                It probably said something along the lines of:

                thunderbird upgraded from 128.3.3-205-1-x86_64 to 128.4.0-206-1-x86_64.

                You can check the installed version via:
                eopkg info thunderbird

                Installed package:
                Name : thunderbird, version: 128.4.0, release: 206
                Summary : Thunderbird Email Client
                Description : Thunderbird is a free email application that?s easy to set up and customize - and it?s loaded with great features!
                Licenses : GPL-2.0-or-later, LGPL-2.1-or-later, MPL-2.0
                Component : network.mail
                Dependencies : libcairo libwebp libxdamage fontconfig libxcb libvpx freetype2 libxext libevent libgtk-3 libxfixes libjpeg-turbo gdk-pixbuf pixman json-c glibc at-spi2 glib2 libstdc++ bzip2 alsa-lib pango libicu libnspr libx11 libnss botan2 zlib libffi dbus
                libxcomposite libgcc libxrandr
                Distribution : Solus, Dist. Release: 1
                Architecture : x86_64, Installed Size: 282.52 MB
                Reverse Dependencies:

                Thunderbird itself will report its version slightly differently. esr isn't a version its a branch I don't know why Mozilla decided to append this to their version numbers but they have. 206 is only relevant to Solus's package manager etc etc.

                EDIT
                If you were talking about this

                thunderbird was updated to 128.3.3-205 (HarveyDevel).

                In the gist linked to in the OP that is because that was true at the time until this:

                Cherry-picked thunderbird 128.4.0

                Source: https://discuss.getsol.us/d/11068-solus-updates-for-week-44-2024/22

                      Great update as always 🙂 I even get now warning for the battery level for my mouse 😃