Xfce, too. Two laptops updatd, starting on my VM collection now. I'm expecting no surprises there.

Everything updated fine, though I noticed when I rebooted that the encryption password prompt on my second monitor (but not the first) was at some crazy low resolution now. It's fine because the prompt appears on every monitor, but it seemed notable.

    pokmu Are you using a Nvidia GPU? If so, which kernel (current or LTS) and which driver (main or beta)?

        Wow 👌 I have nvidia gt1030 on pascal architecture so I'll be interested to join in on the testing team especially when nvidia 560 drivers come out with full open source compatibility

        Plasma update went very well. Another excellent job by all those involved.
        Note to any VirtualBox users. It has been updated from 7.0.14 to 7.0.18. For best experience VBoxGuestAdditions needs an update too.

        Update went well on Budgie, nice work

        Hi there, new to this famous OS
        Did the update right now. All went smooth.
        Only one thing, some of the KDE settings were resetted to default. Like scale, back to 125% instead of 100%. And high of the bottom bar. back to 44 instead of 40
        but marginal.

        Like this OS very well. Like that it's using newest KDE. With newest KDE there's only KDE neon and Tuxedo OS (but both on old Ubuntu), but here I've a stable and updated OS and new KDE. great. Unique selling point.
        Will keep staying here. Big thanks

          Hi,

          178 packages (1,72 GiB) were updated today in Solus Budgie on my computer.

          I actually noticed that the bin/sbin symlink hacks no longer appeared in sudo eopkg check and that's good, because it now makes it possible to better highlight the real anomalies.

          However, I still have some pending that I don't see how to correct:

          Vérification de l'intégrité de linux-current Cassé
          Fichier corrompu : lib64/modules/6.9.10-295.current/modules.builtin.alias.bin
          Fichier corrompu : lib64/modules/6.9.10-295.current/modules.builtin.bin
          Fichier corrompu : lib64/modules/6.9.10-295.current/modules.devname
          Fichier corrompu : lib64/modules/6.9.10-295.current/modules.softdep

          https://0.0g.gg/?effb8ae1ae9307d0#BFBazzRJH5tTdgB2yDLdSbmCQXtYSEDvjGAKSmudSrA2

          Thank you in advance for any help in this regard.
          Best regards.

            EbonJaeger Firefox launches but the window just shows whatever is behind it.

            screenshot

            Edit: I left it open for a few minutes and when I went back it was fine.... But re-launching causes the same issue.

            Terminal output:

            ATTENTION: default value of option mesa_glthread overridden by environment.
[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown
[GFX1-]: Fallback WR to SW-WR
[GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown

                AlphaElwedritsch Hi there, new to this famous OS
                Did the update right now. All went smooth.
                Only one thing, some of the KDE settings were resetted to default.

                Sounds like this might be due to the update from KDE Plasma 5 (which is still the version on the installation media) to KDE Plasma 6. I assume from your text this was a new installation.

                    Staudey No, did a fresh installation a few days ago with 5.27 and updated directly. That gives me an update from 5.27 to 6.1.2
                    The update from today was from 6.1.2 to 6.1.3
                    So, I lost these few settings in 6.1 branch

                      Ok.. found and interesting issue. The latest update/kernel is causing my laptop to run HOT when viewing YouTube or running a vm

                      Hp folio 9470m

                      penny-farthing

                      It is the same underlying issue. eopkg just wasn't updated to ignore that path. You can not correct it yourself and nothing is actually broken.

                          Harvey

                          Thank you for your clarifications, and congratulations to the Solus team of developers for your well-documented work.

                            Just ran a check broken and recieved this after it re-installed linux-current, apparmor, and iptables:

                            [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[FATAL] cbm (../src/bootman/bootman.c:L562): FATAL: Cannot mount boot device /dev/nvme0n1p1 on /boot: No such device