@Lucien_Lachance Please re-enable Top Icon Plus extension, run the following command, and reboot. Let me know if it resolves your CPU usage issue. If so, I'll push it to stable.

sudo eopkg install https://packages.getsol.us/unstable/g/gnome-shell/gnome-shell-3.32.1-41-1-x86_64.eopkg

    I did find one thing broken in Plasma, it doesn't find my sound devices at all, whereas they're fine in Budgie in the same install.

    Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
    driver: snd_hda_intel
    Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
    Sound Server: ALSA v: k5.0.7-114.current

    I had 174(!) packages--like a fresh install!
    But went smooth.

    I am only responding to this post to say noticed I no changes in Budgie. All seems fantastic as usual. I'm noting no font or icon changes or anything else. Graci.

    edit: typo

      there seems to be a small graphical bug, maybe its well known i dont know, when rclicking a folder in nautilus on solus gnome, happens with arc, adapta, plata and adwaita, those are the ones ive tested

        After update, I am booting straight to TTY (not getting the desktop). I suspect it has something to do with the NVIDIA driver, but I do not know what to do - I have nvidia-glx-driver-current installed.

          beerminer I would make sure you've done a full upgrade and don't have broken packages. Run:

          sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

          We have not updated the kernels during this sync cycle, as that is slated for tomorrow by @DataDrake

              beerminer

              1. What desktop environment are you using and with what login manager? (For example, Budgie and MATE default to LightDM+slick-greeter, whereas GNOME defaults to GDM, but you can also use GDM with Budgie or MATE).
              2. What graphics card?
              3. Could you run sudo journalctl -b -e (basically means "show me the system log for this boot, move the pager to the end of the log) and see if you see any greeter, X11, or desktop failures?
              4. Do you have automatic login enabled?

                  I have Solus installed on a 128GB SSD, but it reports that it has a 640GB disk

                    there is also an issue on gnome with apps that are minimized when doing alt-f2+r, they become like ghost apps, some transparent and some not, they cant be clicked and only revert to normal after selecting them in alt-tab or by min/maxing them by other means. big screenshot
                    https://i.imgur.com/FRLsKSP.png

                    JoshStrobl 1. I am using GNOME

                    1. Gigabyte GeForce GTX 1060/REV 2.0 G1 Gaming 6G
                    2. These are the lines with errors:
                      line 744 - failed to query NVIDIA devices
                      line 764 - failed to start NVIDIA persistence daemon
                      line 904 - unrecoverable failure in required component org.gnome.Shell.desktop
                      last couple lines - 2 statements of: gkr-pam: unable to locate daemon control file
                    3. I do not have automatic login enabled.

                        JoshStrobl

                        I'm using Solus Budgie 4.0 and the About section in the Control Center used to show that the main disk is 128 GB. Now, after the update it shows a 640 GB disk, even though it's on the same disk. That's all.

                            brent Re-booted and double-checking since I don't want to eat my words. As far as Icons, my Faba trash can got fat, ugly, and metallic. That is all.
                            Tiredof Faba anyways, so just switched to Paper. It's lovely. File this under 'don't care.'

                              Tourette mine shows 2.2 tb, its a 1tb disk, although i have another 1tb disk with windows, its not mounted

                                beerminer The persistence daemon issue is currently normal and shouldn't affect reaching login. Did you have any extensions enabled for GNOME Shell or PAM modules enabled? If not, I would try:

                                1. Re-installing GNOME Shell, GDM, and gnome-session: sudo eopkg install --reinstall gnome-shell gdm gnome-session
                                2. Resetting world-clocks: dbus-launch gsettings reset org.gnome.clocks world-clocks
                                3. You may have a setting in dconf that is causing issue, you can try moving your settings file: mv ~/.config/dconf/user ~/.config/dconf/user.bak