https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #6 from Flossy Cat ---
(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 sci
https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #5 from Nate Graham ---
I understand it's frustrating for your non-actionable bug report to be closed
as RESOLVED WORKSFORME, but there's a solution to that: make it actionable. If
you aren't able to, maybe any of those people might be able
https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #4 from Flossy Cat ---
It does not work for all those people:
https://bbs.archlinux.org/viewtopic.php?id=281129
https://forum.manjaro.org/t/how-to-troubleshoot-broken-kde-plasma-window-manager/133533
https://forum.garudalinux.org/t/kwin-x11
https://bugs.kde.org/show_bug.cgi?id=491636
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #2 from Flossy Cat ---
(In reply to Zamundaaa from comment #1)
> Please get a backtrace for the crash:
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
https://bugs.kde.org/show_bug.cgi?id=491636
Zamundaaa changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
