Hey everyone,

I hope the sync goes smoothly for all of you. Please note that we are aware of the following items:

  • Adapta: As Adapta is no longer maintained, it has not received any updates to ensure it continues to work well with the GNOME 3.32 series. I would suggest switching to Plata should you find the theming breakages to not be tolerable.
  • Icons look odd: Whether that is Flatpak icons, or stuff like GNOME Terminal using the default icon. For some reason, in specific scenarios the usysconf trigger to clear and update the icon cache is not occurring. You can resolve this issue by running: sudo usysconf run -f.
  • FIX DEPLOYED: High CPU usage under GNOME: Some rare instances of high CPU usage under GNOME has been tracked down to the usage of the Top Icons Plus extension for tray icons. If you can live without tray icons, you can disable it. This is a known issue, see https://github.com/phocean/TopIcons-plus/issues/118 and should be fixed with GNOME Shell 3.32.2.
  • Font changes: Some fonts have been corrected, namely on Solus 4-based installs. This is known and not specifically an "issue", however if you have squishy fonts in the Terminal I suggest you ensure you're fully up-to-date (I did a second sync for additional branding package fixes) and if that does not resolve the issue, please report it to us in #Solus or #Solus-Dev on IRC or on our dedicated GNOME task on the development tracker.
  • The "Open in Software" under GNOME Control Center -> Applications doesn't do anything. I've been working to patch it out entirely, since GNOME assumes we use GNOME Software, when we don't.

For further issues, you're encouraged to report them here and I'll keep a close eye on it!

For issues related to:

  • KDE: Please note that @Girtablulu is on vacation. So please be patient and remember that Plasma is still considered to be in the "testing" phase.
  • MATE: Please ping @kyrios
  • Kodi: Please ping @ermo

    Hmm, my plasma startup first time after 202 items updated, was long enough that I was almost convinced the machine was broken. I haven't restarted again to see if it was a one time thing or what. I'll logout and try budgie too in a few minutes.
    Otherwise, all seems well so far.
    Edit: Nope, Budgie started swiftly. And the next login to Plasma was swift, so apparently something that was a one-time task.

      adapta theme is a bit broken https://i.imgur.com/Mn72HSY.png πŸ™ (i know thats not solus' fault, and that its unmaintained)
      and i dont like plata, so reverted to good old arc which seems fine

      @JoshStrobl it seems the top icons thing is fixed in 3.32.2, i forgot ,what is the solus policy on such incremental updates? will we have them at some stage or are we sticking with 3.32.1 until 3.34.1 (or 3.36.1 or whatever) ?

        Lucien_Lachance We'll be upgrading to GNOME Shell 3.32.2 (and all the other point releases for various GNOME software) when it's released. Right now they're still on GNOME Shell 3.32.1. That being said, I'll look into how trivial it'll be to backport that to our GNOME Shell for the time-being. We only hold off entire GNOME Stack upgrades for the larger updates / new series (so like 3.34).

        Edit: I've updated the original post to have notes about Adapta and more information about Top Icons.

        @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

                            Tourette For me it's reporting correctly.

                            Under inxi -D

                            Drives:    Local Storage: total: 4.77 TiB used: 986.15 GiB (20.2%) 
                                       ID-1: /dev/sda vendor: Kingston model: SUV400S37240G size: 223.57 GiB 
                                       ID-2: /dev/sdb vendor: Toshiba model: DT01ACA200 size: 1.82 TiB 
                                       ID-3: /dev/sdc vendor: Toshiba model: DT01ACA300 size: 2.73 TiB

                            Under GNOME Control Center:

                            4.77 TiB is 5.24 TB.

                              VS Code renders the UI too big, as if it's applying font scaling twice.
                              I also get random GUI lockups from time to time, like everything just stops for about 5 seconds. Always happens at least once soon after logging in.

                                JoshStrobl Oh, so now it summarizes all disks, whether they are mounted or not? Okay then.

                                @mariojuniorjp I deleted your post because it contains an image which shows explicit content in it. Regarding your memory usage, it is indeed likely related to Nautilus file caching. Nothing we can do about it at the moment, we're on an old Nautilus to retain desktop icons.

                                trewdys I'm not able to reproduce your issue with Visual Studio Code (which do note, is not a native application, but rather Electron-based, and therefore not actually affected by our branding package changes as an example). Are you sure you don't just have the view zoomed in? Go to View -> Appearance and at the bottom there is a Reset Zoom option.

                                  Re budgie desktop settings, switching off dark theme doesn’t do anything. Would be nice to be able to turn off.

                                    beerminer
                                    When I installed this round of updates last week (I temporarily switched to the unstable repo) I had the same issue twice.

                                    One time, it occurred out of nowhere (it was not the 1st boot after installing updates), the 2nd time a game played via Wine crashed my system, and it happened after I rebooted.

                                    Both times I resolved the issue by using eopkg history to roll back the update.

                                      Junglist Well we can't investigate and potentially the issue unless you provide comprehensive logs. I would suggest providing those via our development tracker.

                                      Swelch1951 That isn't specific to this stack upgrade, that was the case for Solus 4. I plan on having it be switched to Dark Theme enabled and Plata as the GTK Theme in the future so the toggle works as intended, as well as changing the toggle to appropriately switch between dedicated theme variants (such as doing it for Adapta Nokto as well).

                                      JoshStrobl Was getting nowhere, so I completed a fresh install and then did just the updates (did not install any new apps or remove anything). Now it is hit or miss whether i get the login screen vs TTY when rebooting. On the plus side, both my laptops did fine with the updates...at a loss for the desktop.

                                      I might be hitting @beerminer 's issue as well. After the update I am also booting straight to the TTY (though in my case it is consistent, or at least I haven't been lucky on getting to GDM yet). I am using the built-in amdgpu driver however (with a FirePro W4100 card). In my case it appears that gnome-shell is failing to start on boot:

                                      May 03 13:48:33 myhost gnome-shell[1100]: Failed to create backend: No GPUs found with udev
                                      May 03 13:48:33 myhost gnome-session[1091]: gnome-session-binary[1091]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
                                      May 03 13:48:33 myhost gnome-session-binary[1091]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
                                      May 03 13:48:33 myhost gnome-session-binary[1091]: Unrecoverable failure in required component org.gnome.Shell.desktop
                                      May 03 13:48:33 myhost gdm[1004]: Child process -1087 was already dead.

                                      I'm also not seeing any errors with dmesg or journalctl that indicate that the gpu failed to initialize. Once in the TTY I was able to get to the desktop by running sudo systemctl restart gdm.service, perhaps the issue is that gdm isn't waiting for the gpu drivers to be fully initialized?