@Scotty-Trees triengage I also am having freezing/lockup issues that seem temporary and last for a few seconds. It happens more frequently when I move windows around or accelerated things. Budgie + Nvidia (Latest)

      triengage

      scramble45

      I have this one too. It's because of Nvidia Driver. I uninstall the proprietary driver, and the issue is gone

          Diamond-Dewan It's look like the keyboard applet not picking up ibus input. My japanese ibus input is never shown up in the applet.

            My System is a Solus 3.9999999 updated to a 4.x Fortitude. Budgie. I removed lightdm and used GDM with gnome-shell because I wanted to try Gnome Desktop.

            This Update right here kinda breaks something for me. It didn't start gdm at all. I have not looked into logs tho, I just wanted to have the system running again so I had to re-install lightdm and budgie and remove gdm/gnome-shell.
            I also (re)installed slick-greeter, couldn't remember if it was necessary or not. The Update went fine after that and when I re-enabled lightdm service etc.

            I will try to install gdm/gnome again later on. I will see if it works or not.

            Anyone having Firefox addon issues since this rolled out? Installed addons became unverifiable and new addons cannot be installed at all :/

              My Screen "Dims" after inactivity while watching videos.
              Still happens if I turn it off.
              Using Budgie.

                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.

                Should I open an issue upstream for that?

                  -r- No, it's distro issue. Because Solus not using Gnome Software.

                  • -r- replied to this.

                      I'm still getting freezes and hangs that last 3-7 seconds all the time. Even trying to resize windows, it freezes. System is pretty unusable in this state with the constant freezing, but I'm willing to stick this out and figure it all out with you guys! Perhaps the new kernel push later today might fix that, but I do not know for certain. Like I mentioned I'm on Solus 4 Gnome, using proprietary nvidia glx drivers current on the latest kernel 5.0.7-114.current

                      I don't know if I was supposed to do this or not, but after I had ran the sync using sudo eopkg up, I rebooted and ran these commands as well, feel free to let me know if I was supposed to OR if it was okay or not to run these commands:

                      sudo usysconf run -f
                      sudo eopkg rdb
                      sudo eopkg up
                      sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

                        In Settings > Sound the volume bar doesn't seem to register anything, it works for microphone. Test sounds don't play either while sound is working fine.

                        yursan9 Well, it's up to GNOME to show that button dynamically if someone is using only part of their eco-system. Provided there wasn't some Meson flag the packagers missed...

                          Scotty-Trees I'm having the exact same problem. CPU spikes and 3 or 5 sec freezes all the time, making the system unusable. I'm not sure where it's coming from. Glad to see I'm not alone.
                          I'm not using topicons-plus and all updates have been installed, including manually installing gnome-shell-3.32.1-41-1-x86_64.eopkg (which according to Josh, shouldn't be necessary). I'm on Solus 4 Budgie, current kernel and nvidia drivers.

                              Yea, the issue has been reported in various places such as: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 and is (fortunately) not an issue limited to Solus. There is a WIP change to st that should alleviate it but as you can see from their merge request discussion, there has been discussion that this MR indeed reduces the amount of style-checked calls, but may introduce further issues (so they've been thinking about reverting it). That specific MR affects GNOME Shell, so still need to look elsewhere for the Budgie issues.

                              I'm going to get this tested on unstable regardless. I'm sorry that some of you are experiencing these issues, working to get to the bottom of it.

                              Nibb31 If you're on Solus 4 Budgie, then you're using Budgie, not GNOME Shell, and thus an update to a completely different desktop environment wouldn't help much.

                                Updates From Unstable

                                Please note that the below mentioned commands should only be run if you are willing to test packages from the unstable repository. These changes are a WIP, may be reverted, and may result in unexpected instability. That being said, our best way of finding out if the fixes actually...well fix things, is for people to test before we opt to sync (or not). Please report if it improves, degrades, or doesn't change your performance.

                                Some testing alongside @Scotty-Trees reports that the branding package updates should be the primary factor for performance fixes under GNOME. I'd like to thank him for working with me on identifying and testing the fixes.

                                This issue may also affect some individuals not getting to the login screen if they're using GDM.

                                Regardless of the command use, please reboot after you install the respective packages.

                                Budgie

                                If you are using Budgie, you are likely going to need to install specific branding sub-packages, so please do not immediately run the below mentioned command:

                                sudo eopkg install https://packages.getsol.us/unstable/m/mutter/mutter-3.32.1-48-1-x86_64.eopkg
                                Branding

                                You should run eopkg li | grep 'budgie-desktop-branding' to get a list of Budgie desktop branding packages you have installed. Please append (add to the end) of the above command (which specifies to install mutter), the following eopkg links depending on what you have installed. You may need to specify multiple:

                                If you are using Budgie with GDM (you'd know because you'd also have GNOME Shell installed), see the GNOME section too.

                                GNOME

                                If you are using GNOME Shell (or co-installed with Budgie, in which case just append the eopkgs listed below, eliminating duplicates), run the following command after adding the branding packages (listed in the branding section below)

                                sudo eopkg install https://packages.getsol.us/unstable/m/mutter/mutter-3.32.1-48-1-x86_64.eopkg https://packages.getsol.us/unstable/g/gdm/gdm-3.32.0-45-1-x86_64.eopkg https://packages.getsol.us/unstable/g/gnome-shell/gnome-shell-3.32.1-42-1-x86_64.eopkg
                                Branding

                                You should run eopkg li | grep 'gnome-desktop-branding' to get a list of GNOME desktop branding packages you have installed. Please append (add to the end) of the above command, the following eopkg links depending on what you have installed. You may need to specify multiple:

                                Changes

                                • Budgie Desktop Branding: We're now exporting __GL_MaxFramesAllowed=1 in a new dedicated profile.d file. See this commit and reference bug report here.
                                • GDM: Test GDM load failures by disabling Wayland support (this has always been deemed experimental, we need to disable it here because it breaks X11 fallback) and swapping to VT1 (despite it being a CLI VT, it's what GDM defaults to for some reason). I was able to reproduce in my local testing the issue with it loading GDM but not switching to VT7 to actually show it. Reference Commit
                                • GNOME Desktop Branding: We're now exporting __GL_MaxFramesAllowed=1 in a new dedicated profile.d file. See this commit
                                • GNOME Shell: Add various St patches to reduce style-changed calls. These patches are currently in the master branch of GNOME Shell as opposed to gnome-3-32 and should reduce style-changed calls by several hundred (estimated from 700 to 110) as reported in this merge request. This commit also includes follow-up patches to that MR which should alleviate some of the concerns around patch reverting. Reference Commit.
                                • Mutter: Backported various patches that are in the gnome-3-32 branch but not yet in a point release. Reference Commit
                                  • compositor: Destroy window actors list on destruction
                                    • When the compositor is destroyed we should cleanup the list of window actors we created and destroy them.
                                    • Destroying the window actors instead, ensures we avoid any further call to X11 related functions and that we release the actors XServer resources.
                                  • compositor: Disconnect from stage signals on destruction
                                    • From this point there's not any need for the compositor to listen to signals so we can disconnect from the stage ones we are connected to.
                                  • backends: Fallback to builtin panel for devices where all heuristics fail

                                Note

                                For those on the stable repo that do not wish to test these, do note that once these are synced, you just need to upgrade. You will not need to manually install any eopkgs.

                                Tagging Affected Users

                                @Scotty-Trees @Nibb31 @nodq @scramble45 @triengage @ReillyBrogan @beerminer