@WetGeek I just tested this out under both my systems and I am unable to reproduce. Are you using proprietary graphics drivers and if so, which?

    WetGeek Note that this does not occur on MATE. I checked that on our media computer.

      JoshStrobl I am unable to reproduce. Are you using proprietary graphics drivers and if so, which?

      Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
      chip ID: 8086:0416
      Device-2: NVIDIA GK106GLM [Quadro K2100M] vendor: Dell driver: nvidia v: 390.138 bus ID: 01:00.0 chip ID: 10de:11fc
      Display: x11 server: X.Org 1.20.8 compositor: budgie-wm driver: modesetting,nvidia display ID: :0 screens: 1
      Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
      Monitor-1: eDP-1-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5")
      OpenGL: renderer: Quadro K2100M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.138 direct render: Yes

          WetGeek If you open up NVIDIA X Server Settings via Budgie Menu then go to X Screen 0, what are your settings for:

          • Sync to VBlank
          • Allow Flipping

          Additionally if you click X Server Display Configuration then click the "Advanced..." button in the bottom, do you have any of the following checked:

          • Force Composition Pipeline
          • Force Full Composition Pipeline

          Looking at some Mutter changes that landed after 3.36.3 but that was in previous sync so shouldn't be a sudden change there. It may be related to the nvidia-390-glx-driver update. Once we get the settings, we can see if reverting the 390 for your system specifically fixes the issue.

              JoshStrobl I am unable to reproduce.

              Almost certainly a driver issue. My wife's ASUS laptop does not exhibit this problem, and like most of our computers, that one is running Budgie as well. Do you have a recommendation for a driver change?

                  WetGeek Could you run: eopkg li | grep 'nvidia-390' for me so I can get a list together of drivers for you to install? Thanks!

                    nvidia-390-glx-driver-common - Shared assets for the NVIDIA 390xx GLX Driver
                    nvidia-390-glx-driver-current - NVIDIA 390xx Binary Driver (Current Kernel)
                    nvidia-390-glx-driver-modaliases - These files are used by the Software Center for hardware detection
                    r

                      WetGeek Try the following (after installation, reboot)

                      sudo eopkg install http://mirrors.rit.edu/solus/packages/unstable/n/nvidia-390-glx-driver/nvidia-390-glx-driver-common-390.132-69-1-x86_64.eopkg http://mirrors.rit.edu/solus/packages/unstable/n/nvidia-390-glx-driver/nvidia-390-glx-driver-current-390.132-69-1-x86_64.eopkg http://mirrors.rit.edu/solus/packages/unstable/n/nvidia-390-glx-driver/nvidia-390-glx-driver-modaliases-390.132-69-1-x86_64.eopkg

                      These drivers should work since they were build against the kernel I rebuilt against OpenSSL, whereas release 70 (which came after and is on stable / shannon now) was the update to it.

                          JoshStrobl open up NVIDIA X Server Settings via Budgie Menu

                          Sorry, can't find that in Budgie Desktop Settings or in System Settings.

                              WetGeek Sorry, can't find that in Budgie Desktop Settings or in System Settings.

                              Via Budgie Menu, not settings. It's a dedicated app provided by NVIDIA.

                                  WetGeek No problem. I will see about reverting this on unstable and getting it pushed to shannon / stable once the sync is done. Should you see an update, it'll be a release for 390.132-71. It will be safe to update to that 🙂

                                    JoshStrobl Via Budgie Menu, not settings.

                                    Sorry, I took Budgie menu to mean the default menu in Budgie. I need to install Budgie Menu and familiarize myself with it. Sounds interesting.

                                        WetGeek Sorry, I took Budgie menu to mean the default menu in Budgie. I need to install Budgie Menu and familiarize myself with it. Sounds interesting.

                                        You said Budgie Desktop Settings, hence my clarification. Budgie Menu comes with Budgie, it is the menu.

                                        Either way I believe it is an issue with the PRIME Synchronization feature they added in the latest 390.xx release, so I reverted and pushed that to unstable. Will do a follow-up cherrypick after sync 🙂

                                            I had to rebuild my Realtek WLAN drivers, as wireless connectivity disappeared following the upgrade (running Solus Plasma). This was easy, following directions elsewhere on the forum, and now everything is running flawlessly.

                                            JoshStrobl Budgie Menu comes with Budgie, it is the menu.

                                            Thanks for the clarification. I'd never needed the Budgie Menu before, so I didn't know to search for it. Now I do.

                                                JoshStrobl Additionally if you click X Server Display Configuration then click the "Advanced..." button in the bottom, do you have any of the following checked:

                                                Force Composition Pipeline
                                                Force Full Composition Pipeline

                                                JoshStrobl Either way I believe it is an issue with the PRIME Synchronization

                                                @WetGeek

                                                I could be way off base here as I own ZERO mobile nvidia stuff.

                                                But PRIME does not have forced composition options. You have to do this:
                                                echo "nvidia-drm.modeset=1" | sudo tee /etc/kernel/cmdline.d/50-nvidia-drm.conf
                                                sudo clr-boot-manager update

                                                I only know due to @Scotty-Trees 's past screen tearing issues for which this is the equivalent fix.

                                                    WetGeek rel 71 is in shannon now, please update and let me know if it's still fixed. Thanks!

                                                        JoshStrobl el 71 is in shannon now, p

                                                        I updated (3 pkgs), rebooted, and tested with kshisen. This is still showing the same issue as before.

                                                        I liked your ad-hoc fix a lot better. 😀

                                                            WetGeek This is still showing the same issue as before.

                                                            That doesn't make any sense since you're literally on the same software release that 69 was. So yea, sounds like a separate issue entirely. Might want to take a look at @Harvey's solution.