Bug 382812

I'm sorry, but the mouse icon is not in the responsibility of the X11 window manager. This is either a bug in the nvidia driver or in X, but not in any software KDE provides.

I'm sorry too.
I had my nvidia and associated packages pinned, so I'll roll back the xservers one at a time and see which one caused the problem.

There is a simple workaround to fix this.

If you logout of Plasma, then re-login the issue goes away.

So for time being you can workaround by

- booting up neon (to sddm login)
- go to a tty (ctrl+alt+f2)
- login then use

# sudo systemctl restart sddn

- login 
-> Issue has now gone until the next reboot...

I think its an Xserver issue rather than Nvidia as the older driver (which was fine is now having a same issue)

sorry the correct command is

# sudo systemctl restart sddm

Guys, I have the same exact issue and I have no idea why you keep on saying this is "resolved". (https://bugs.kde.org/show_bug.cgi?id=382865)

Gnome works perfectly on the same computer, with the same Xorg and nVidia drivers.
This is clearly a KDE bug appeared a few days ago, most likely after an Xorg update.

Note that I am using KDE Neon too, so isn't the Neon team responsible to test and certify upstream packages before delivering them to the masses, to guarantee a consistent KDE experience ? Or are we really left to ourselves even on a KDE product ?

For the record, this issue makes it impossible to use KDE, so I am using Gnome these days, which is disgusting for me after 15 years of KDE.
You're really letting us down with this "point the finger" game.

(In reply to Massimo Callegari from comment #5)
.....
> 
> For the record, this issue makes it impossible to use KDE, so I am using
> Gnome these days, which is disgusting for me after 15 years of KDE.
> You're really letting us down with this "point the finger" game.

Nonsense.  The workaround mentioned by Morgan Cox works beautifully.  This issue will probably be resolved with the next 4.8 kernel update.

(In reply to Massimo Callegari from comment #5)

@Massimo Callegari 

This isn't a KDE only issue, I get the same thing if I use openbox via sddm.

It could potentially be an sddm issue or more likely the updated xorg version.

Yes, it is annoying however you can still use KDE fine, just restart sddm before you start using it...

> Guys, I have the same exact issue and I have no idea why you keep on saying
> this is "resolved". (https://bugs.kde.org/show_bug.cgi?id=382865)
> 
> Gnome works perfectly on the same computer, with the same Xorg and nVidia
> drivers.
> This is clearly a KDE bug appeared a few days ago, most likely after an Xorg
> update.
> 
> Note that I am using KDE Neon too, so isn't the Neon team responsible to
> test and certify upstream packages before delivering them to the masses, to
> guarantee a consistent KDE experience ? Or are we really left to ourselves
> even on a KDE product ?
> 
> For the record, this issue makes it impossible to use KDE, so I am using
> Gnome these days, which is disgusting for me after 15 years of KDE.
> You're really letting us down with this "point the finger" game.

(In reply to Jerry L Kreps from comment #6)

Its not kernel related, neon is using kernel 4.10 now, it occurs on both 4.8 + 4.10 but has only started occurring since plasma + xorg update (they updated at the same time so don't 100% know which - i assume xorg)

> (In reply to Massimo Callegari from comment #5)
> .....
> > 
> > For the record, this issue makes it impossible to use KDE, so I am using
> > Gnome these days, which is disgusting for me after 15 years of KDE.
> > You're really letting us down with this "point the finger" game.
> 
> Nonsense.  The workaround mentioned by Morgan Cox works beautifully.  This
> issue will probably be resolved with the next 4.8 kernel update.

This started happening on my computer in all applications after a recent update (probably in July 2017) as I mentioned in Bug #381533 . The issue went away after disabling "Enable Compositor on startup" which is under System_Settings->Display_and_Monitor->Compositor and then restarting. 

Update: I just noticed if I use Google Chrome, it occurs, but only in Google Chrome even with compositor not enabled on startup. 

The command 

sudo systemctl restart sddm

as mentioned in Comment #4 worked to fix the mouse issue appearing in Google Chrome.

Please stop reporting further comments in this report. THIS IS A BUG CAUSED BY THE UPDATE OF THE NVIDIA DRIVER! IT IS NOT A BUG IN OUR SOFTWARE!

Reporting here just doesn't reach those who could fix it.

Thank YOU!

Martin, Almost certain it is not the Nvidia update that has caused this..

I have been happily using nvidia 381.22 for months with no issues, this occurred after kernel/xorg hwe updates (to neon) - I got this error *before* updating the nvidia driver to the latest stable - the issue appeared only after installing xorg and kernel updates...

Also note : I do not have this issue @ home desktop on my nvidia 1060 (same OS, drivers, etc) - it could be related to hybrid GPU's the issue is on my work laptop with hybrid gpu.

I do undestand though this is not a KDE issue (as I stated earlier, unless sddm specific)

(In reply to Martin Flöser from comment #10)
> Please stop reporting further comments in this report. THIS IS A BUG CAUSED
> BY THE UPDATE OF THE NVIDIA DRIVER! IT IS NOT A BUG IN OUR SOFTWARE!
> 
> Reporting here just doesn't reach those who could fix it.
> 
> Thank YOU!

Instead, writing in caps will help to fix the issue, will it ?

I confirm this has nothing to do with nVidia drivers, and I suspect too this has been caused by xserver-xorg-core-hwe (just checked my logs)

In any case, as I stated before, Gnome didn't suffer from this update, while KDE (or sddm) did. And again, as KDE Neon users, where else would we report this issue ?
YOU guys provide KDE Neon. YOU take the responsibility for the mess that untested package deliveries cause to your users.

Otherwise everybody in this world would be able to make a distro and then point the finger when things go wrong.

I checked regarding the Nvidia comment. 

Upgraded to Nvidia 375 ( nvidia-375:amd64 (375.39-0ubuntu0.16.10.1, automatic) ) on 2017-04-05 

Upgraded to Ubuntu 17.04 on 2017-06-08  

The issues only started to happen (as far as I noticed) after upgrades in 2017-07 which did not include any Nvidia updates.

Reassigning to neon: not a bug in KWin, users complain about the regresssions due to rolled out updates in the lower stack.

When I boot from my previous kernel, 4.4, I have no mouse problems, even though I am using the same nvidia 378 driver with 4.4 as is used with 4.8.  After I boot into 4.4 I can do a warm reboot into my 4.8 kernel and the mouse continues to work normally.  However, the workaround given by Cox, restarting sddm, is a lot faster and works well.

Note that neon developers only maintain the KDE software, everything else, including kernel and xorg, are used directly from Ubuntu.

Martin reassigned this to neon developers. Maybe they find a way to test Plasma integration with proposed changes from Ubuntu before they hit the update repositories.

Do we need to open a bug report on ubuntu bug tracking for Xserver ?

Workaround would be to restart sddm twice on boot (not elegant)

this is definitely not only KDE Neon specific, this issue takes place on I guess every Ubuntu based OS that use KDE Plasma 5, I did a clean system installation of KDE neon and got this issue, thinking it might be because of KDE Neon I went back to Kubuntu 16.04 (also a fresh install) and the issue appeared again when my system was enabled to use Nvidia instead of Intel card. This annoying bug affect KDE users on various distro basis ( as seen mostly Ubuntu based) and has something to do  with the latest updates (up until writing of this comment), KDE Plasma 5 ( older and latest releases) and systems with Nvidia cards ( as far as I was able to track).  Note that other DEs doesn't seem to have this issue, KDE Plasma 5 developers should put some eyes on this, we don;t want to see users not recommending Plasma 5, it is too awesome to be ruined by something like this. It might look like a small issue but it ruins the usability to the most common daily tasks, that is really not good.

The bug is NOT only KDE Neon. It has been happening in Kubuntu ever since upgrade to 17.04 and it was not because any nvidia upgrade. It remains exactly the same today, with all possible ubuntu updates. Workaround: log out and login again.

It is interesting that there are so many bug reports open for this bug in bugs.kde.org (at the very least: 381533, 382865 and 382812) and it keeps being pointed as "somebody else" problem, ranging from nvidia, KDE Neon, X11, etc.

It looks as if a normal user that just wants to switch on her KDE system and sees that it won't work as advertised, only has the option to become a developer in order to determine herself what exact line of code is broken, instead of simply complaining to the KDE developers to figure it out themselves.

It is very sad to see that users do not have the possibility of even just reporting a problem without getting a finger "talk to somebody else, we don't know". That's the point.

What do you do when you find a "bug" in your TV set: do you go to the vendor and complain or do you start figuring out yourself every single possible component of that system that could be failing to avoid the unpleasant response "not our problem"?  Could you at least lead all the users in a decent direction that doesn't involve quitting using KDE at all?

This bug is still present.

If we are meant to be reporting this elsewhere can someone explain where ?

For the sake of it, and since restarting SDDM every time is VERY annoying, there's another workaround found here
https://bugs.launchpad.net/ubuntu/+sour ... ug/1684240 - #16

Go to KDE System Settings -> Display and Monitor -> Compositor (left side) -> set "Rendering Backend" to XRender

Sorry, broken link. That should be
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240

Thanks @Massimo Callegari


However using Xrender isn't really a good solution, really you are wasting your GPU using that.

At least after sddm restart everything does work normally with full h/w compositing.

This is a really annoying bug and I know for a fact it has caused friends who wanted to try out neon to abandon it (some reinstalling Windows..)

@Morgan Cox I didn't say it's a solution. It's another dirty workaround to compensate a SDDM bug.
Turns out XRender compositing affects VLC too which is pretty bad.

Another 'workaround' is to use 'slim' instead of SDDM.

I thought about opening a ticket in the SDDM GitHub page...but they have 200+ open issues and doesn't seem they care that much. I think SDDM should be abandoned for good.

And I do totally understand your comment about Linux newbies. At the moment I don't feel suggesting Neon/Plasma to anyone either.

(In reply to Massimo Callegari from comment #25)
> @Morgan Cox I didn't say it's a solution. It's another dirty workaround to
> compensate a SDDM bug.
> Turns out XRender compositing affects VLC too which is pretty bad.
> 
> Another 'workaround' is to use 'slim' instead of SDDM.
> 
> I thought about opening a ticket in the SDDM GitHub page...but they have
> 200+ open issues and doesn't seem they care that much. I think SDDM should
> be abandoned for good.
> 
> And I do totally understand your comment about Linux newbies. At the moment
> I don't feel suggesting Neon/Plasma to anyone either.

I have discovered that Kubuntu 17.10 isn;t affected by this bug. 
Quite some time has passed since my last time checking on this bug. So I decided to give Kubuntu and Kde Neon another go, since I heard there were some updates and wanted to see how it works as I wanted to go back to 16.04 LTS but both KDE Neon and Kubuntu 16.04 with latest greatest updates gave me the damned cursor bug with Nvidia drivers. tried different version, no difference. Then I thought what if it was kernel related, Kubuntu 17.10 comes with a newer kernel which at the time was 4.13 so I upgraded my Kubuntu 16.04 to Linux Kernel 4.13 and the issue is still there. Again went through many recommended workarounds and none seemed to be the good one. Went back to Kubuntu 17.10 again and have no damned cursor bug. A good starting point too look at might be the differences between Kubuntu 17.10 and Kubuntu 16.04  because Kubuntu 17.10 seems to have it solved for the users.

I can confirm that after upgrading my Kubuntu system from 17.04 to 17.10 the problem is not happening.

I have to say that the real bug is/was never whatever they fixed. Honestly, after all these, whatever it was doesn't really matter:

The real bug *IS the bad attitude* that _some_ (but an ever increasing number too!) KDE devs have adopted as standard, that generate ultra-defensive replies (if any at all). In some cases, it might not be bad personality or bad character: It might be a worrying sign of something else altogether.

While I --having myself been victim of burnout like many others-- understand the symptoms of that condition and how important it feels to kick out any problems as small as they might be when you are in such condition, the cruel truth is that until recognize and accept what you are going through, you are just going to get worse. You'll find yourself raising your voice (or writing all in caps) more often than you would normally do before, and failing to make good decisions because frustration takes over the best of you.  With all sincerity and good will, I strongly advise those who are felling like that, to seek for professional help before it's too late.  For those who are just jerks, I think they should abandon the FOSS community altogether.

I have been watching many threads in the KDE bug tracking and it's really scary what I see. As user, I must say that this really is getting the prize of the least friendly community and frankly the least helpful I have seen since a few years already. Of course with honorable exceptions: those reading will know. If not, please just spend a little more time reading through threads of this bug tracking system or just try and open a new one yourself.

IMHO I think that the KDE project as a whole, should look at those devs that are burned out or in their way to that: they should not be allowed to "help" in this bug tracking system. I am not being sarcastic, I seriously mean that.

The next sentence _is_ sarcastic, but I hope it somehow helps to make this dramatic point clear and no offence intended: To tell people that "this is not a KDE problem go complain somewhere else", an automatic script would suffice, no overwhelmed human needed.

Well thanks to the Spectre flaw 16.04.x users (including kde neon) are getting a new version of the kernel in the next day or so - at least those running the hwe kernel - presently @ 4.10.x - we were getting 4.13.x anyway in Feb but this has been sped up due to the issue.

https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown

Who knows this may fix the issue (I really doubt it however)

The cruel truth is that the bug you saw was not a bug introduced by KDE developers. Since it's resolved at the underlying packages, let's close it.

I have KDE NEON with KDE 5.11.5 and Kernel 4.14.13-041413-generic. This BUG NOT IS RESOLVED. 

I have this bug from April of 2017. I can't use my video card Nvidia, i have that use my intel video card. When it will be fix?

Thanks.

It is fixed in latest Xorg. You will have to wait until Ubuntu LTS rolls out the updates, or install from a backports repository.

*** Bug 388750 has been marked as a duplicate of this bug. ***

*** Bug 397403 has been marked as a duplicate of this bug. ***