@GZGavinZhao I'm not a power user of Sayonara by any means. I just came back to it after a few months of using Lollypop because the latter add issues displaying manually added cover pictures. So I'm not sure I've tested all features commonly used by other users. But I've tried navigating the app, it's menus and playing files from my local library and everything seems fine. No regressions that I could find. Thanks a lot for the package!

@Staudey The nvidia-drm.modeset=1 kernel is a standard solution to get rid of screen tearing issues on Nvidia Prime laptops, since they lack certain options in Nvidia's settings tool. See Harvey's survival guide post in the forums for reference. I've had this parameter set this way for as long as I've been using Solus (nearly 3 years now) and it's never caused me any issues before...

As for disabling the integrated GPU in the bios, I looked around but couldn't find any option for it. I think my laptop (Lenovo ThinkPad Edge 530) does not support this functionality and the dedicated GPU is rather a co-processor, where the integrated GPU is the only connected to the display and needs to be enabled for any display to the laptop's screen to work.

@kaktuspalme Thanks for the help!

@Staudey Any updates on this issue, given that the problem is quite critical?

I should have mentioned it in my original post, but I made absolutely sure everything is up-to-date. To confirm for nvidia-glx-driver-current, here is the info you requested:

Installed package:
Name                : nvidia-glx-driver-current, version: 460.32.03, release: 365
Summary             : NVIDIA Binary Driver (Current Kernel)
Description         : NVIDIA Binary Driver (Current Kernel)
Licenses            : EULA
Component           : kernel.drivers
Dependencies        : linux-current nvidia-glx-driver-common 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 43.21 MB
Reverse Dependencies:

I can confirm I've got the same problem since at least the December 18th Solus update. However, in my case, no concurrent updates happened for my device (Galaxy Tab S6 Lite running Android 10 November update). I noticed the issue following the December 18th update, but it had been a while since I tried to move files to my Samsung device. So I'm wondering if the issue was ultimately caused by the Nautilus or kernel 5.10.x update, although it seems limited to Samsung devices because I can't reproduce it on my Pixel phone running Android 10 either.