https://bugs.kde.org/show_bug.cgi?id=382812
ocumo <kxk-ocumoatbugs...@lugosys.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kxk-ocumoatbugskde@lugosys.
| |com
--- Comment #20 from ocumo <kxk-ocumoatbugs...@lugosys.com> ---
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?
--
You are receiving this mail because:
You are watching all bug changes.
