Does it work properly on Windows, after installing NVidia's drivers?
We should verify whether this is a software or hardware issue (or possibly firmware issue, but I'm not holding my breath for that).

No idea. I don't have windows

You can try installing Windows 10 (no need for a license, since it would only be for a few hours), and check if the issues persist after installing NVidia's drivers.
If they do, I'd recommend filing a warranty claim, but if not, then we can continue diagnosing this issue.

To say the truth, this sounds like a VRAM issue to me, but it may be completely unrelated (I'm no expert).

Can you try rolling back to stable drivers and see if the issue persist.

@sahilarora3117 he's already running them.
The newer GTX cards (I think starting from 8xx or 9xx series, I forget precisely which, as I do not have such hardware on me) don't allow reclocking without a signed firmware image, so you cannot truly test for hardware issues without the closed source drivers.

Hi !

I'm having the same issue for about a month with my GeForce GTX 1050 on an Asus UX550VD (running Solus Budgie).
I noticed that the cursor glitch seems to be only present when the 32b driver is installed.

It's quite random. Hasn't happened to me in a while.

I have the same problem running on a GTX 1060 Q-Max on a Dell G5 15.
It never happened on Fedora 29 and Ubuntu (I think the driver on Fedora was not the 415)
And I confirm that it seems to be solved when 32 bits drivers are not installed

I am also having this problem (Solus Budgie). I have a GTX 960M (in combination with Intel HD Graphics 530).

The following two reports might be related:
https://dev.getsol.us/T7276
https://dev.getsol.us/T5747

Uninstalling the 32 bits drivers did not solve the problem for me. What always helps is a logout (suggested in one of the posts in https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240).

Hi,

Just to confirm, I am also having this issue on my Dell G3 15 with 1050 Ti with 32bit drivers installed. I noticed this first around the middle of January but I can't remember the exact date and which update caused it.

Regards,

Ravi

Hi,

I was shown a link to Ubuntu bug report around this (https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240).

There are some different workarounds proposed in that link however one that works for me is to log out and log back in once you have first booted into your user account. This consistently works for me and only takes around 15 seconds after first boot before I can get using my laptop. Whilst not a solution, it seems to be a workable temporary fix.

I haven't experienced this issue for 6 months, can we close this or is the bug still present in somebody's laptop?

In T7368#153167, @Juankz wrote:

I haven't experienced this issue for 6 months, can we close this or is the bug still present in somebody's laptop?

Yes,

I did a fresh install of Solus a couple of weeks ago and this bug still occurs for me. I am keeping everything up to date including graphics drivers etc. I'm still using the workaround where I log out and log back in after first boot to fix the issue until the next restart.