Comment 6 for bug 1684240

Finally found the bug report of this problem. It affects me, exactly the same. I could provide more details BUT it doesn't seem to be relevant, doesn't it? I explain:

A couple of notes, @jgrns:
What do you mean "the problem disappeared"? Does it mean: it "disappeared" from your system? Or: on everybody else's systems? It didn't "disappear" from mine. Mind to provide any useful context?

Posts like that are the ones that make so many people hate 'this' (you know, Linux, FOSS, and all the things that they should not hate for things like this). Not because you are inaccurate and confusing, but because you seem to have the power to change the status of the bug (without actually fixing it), whatever "nouveau" means in your launchpad jargon.

The bugs reports are not to satisfy those who have the power of changing status of bugs. They are for the users, because without users software is useless. Far too frequently I see these useless posts that seem to imply that magic does exist.

Problems don't "disappear" by magic in Engineering or in Science or in Life. And if you think they do, at least you should propose some theory that doesn't make you look that you just want to dismiss the problem or make us believe that "if you wait long enough, all your problems in life will disappear" --which is true, but some us don't want to wait until we die to see all troubles vanishing from our lives. I would be fired if I would ever suggest that to my customers, or worse, tell them that because all of a sudden I ceased to see the problem, they are wrong and it doesn't exist.

Sorry if it looks that I am irritated, but those six words did the job. I am sure others with this problem would also feel. Please if you can't help with this bug, or believe it's something magical that comes and go, or if open tickets are annoying, then please at least don't dismiss it with "it disappeared" without at least a slight context. It doesn't really add credibility to a --presumably-- software developer who tells users with a complaint that the problem was perhaps abducted by aliens and now "is gone". It's not. It's a bad bug, it disrupts tremendously the work in the KDE environment, to the point of almost preventing us to work with most of the programs that use the mouse at all. It is a show stopper.

You can change the status of the bug to whatever you please, it's not "my" bug report system. But then it's a bit useless for the rest of the people.

Anyhow, thanks for the bug report, because it is very well described. I might copy/paste part of the description and seek for help somewhere else.