https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #6 from Flossy Cat <[email protected]> --- (In reply to Nate Graham from comment #5) > I understand it's frustrating for your non-actionable bug report to be > closed as RESOLVED WORKSFORME, This is not about frustration, but about attitude. I'm computer scientist, SW-engineer and project trouble-shooter with 40+ years experience, hunting difficult bugs since (and since 1986 in FLOSS). So, I completely understand, that – while I delivered what was available in the system – that is not much to work from. Read the following as "from professional to professional" and not as rant! I could perfectly well live with REPORTED and WAITINGFORINFO – because that would be factually correct and might later contribute to a more complete view when similar bug reports with other indicators pop up. Closing the issue is IMHO wrong both on the process level as well as in social communication. WORKSFORME as a state conveys gross impoliteness, disinterest and neglect as well as communicates a very egomaniac perspective not in concordance with the spirit of a community. It further communicates, that KDE doesn't care both about problems in crucial components like kwin (or KDE-PIM, see my the corresponding bug reports) and the problems KDE user experience (again, see my KDE-PIM bug reports). In German we have a shorter term for WORKSFORME: LMAA … I was a fervent user and advocate of KDE for a quarter of a century – with much heartache I'm migrating away from KDE-PIM, which was the main reason for still using KDE. Having worked on many ailing and failing projects professionally, I recognize many warning indicators in many KDE elements (programs, docs, foundation). What is your perception as QA manager by profession? > but there's a solution to that: make it actionable. If you aren't able to, > maybe any of those people might be able to. So far the crash did not repeat – I check regularly for systemd-coredump collecting a core-dump (as OpenSUSE already has a counter-measure by having systemd restarting kwin, a repetition could go by without noticeable effects …) As you see from the links: I did research and I'm providing the information I'm able to collect. Obviously "those people" don't care, and – with the exception of my Kalarm bug reports – I have still to see any level of care of spirited bug resolution for the KDE LTS version at KDE-BUGS. > Bug reporting is a technical process that demands something from the bug > reporter too. See > https://community.kde.org/Get_Involved/ > Issue_Reporting#Issue_reporting_involves_responsibility. Where do I not follow my responsibility? > The issue with being unable to get a backtrace for KWin was solved in Plasma > 6 which was released 6 months ago, but unfortunately you're still on Plasma > 5, so that doesn't help either. There have been so many KWin changes since > Plasma 5.27 that it's quite possible the issue is already fixed anyway. It > could also have been fixed in a newer Mesa, Kernel, etc. Bug reports on old > software like this one often end up in such a state; it's just the way > things are. Using more up-to-date software definitely helps to make bug > reports more actionable. As given in the version section: I'm using OpenSUSE LEAP 15.6 which is current software which uses the current KDE LTS version. I use my systems for productive work and this precludes manually compiling or installing leading edge versions, because I need timely security patches. This is state of the art and not open for discussion. This professional stance should be embraced by KDE. What sense does a KDE LTS version make, if KDE does not consider itself bound by the promise of *Long Term Support*? If the only choice is "bleeding edge with continuous nasty surprises" vs. "live 2 years with bugs till repaired versions trickle downstream into well-maintained distributions", my choice is clearly the 3rd option: Switch the desktop and the tool-set. That definitely WORKSFORME and RESOLVES my problems. -- You are receiving this mail because: You are watching all bug changes.
