https://bugs.kde.org/show_bug.cgi?id=407784
razangriff-ra...@tutanota.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|UPSTREAM |---
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
--- Comment #17 from razangriff-ra...@tutanota.com ---
Please listen to what I am saying. How can it not be a kwin bug when it
explicitly depends on the version of kwin? Why does it happen with the current
version of kwin ONLY but not the previous version of kwin? I have even tried to
update other packages while holding back kwin in particular and the freezing
only, ONLY happens when kwin is updated past 5.15.5. Why do the windows
magically unfreeze themselves when shutting kwin down, or forcing kwin to
refresh? Why does it not happen with any other window manager, composited or
not? Why is kwin so ubiquitous in this whole mess when it has nothing to do
with anything, despite everything I'm reporting?
You are ignoring my previous reports entirely. I DID mention the problem
happened whether composition is active or not, I only keep it disabled by
default because it adds extra overhead. I am not an English speaker, thank you
for your patience.
You have not asked for a single bit of data to actually help, and only tried to
dismiss it deflecting the blame or something. This is why I and many others
never bother reporting KDE bugs. What is with that attitude? I know the user is
implied to be an idiot, but don't give me that, I am not linux-illiterate, I
know enough about my system to know the problem is linked to kwin because it's
the only component that causes the problem when updated. You think I didn't
bother testing first? I did more testing than you did! I only got asked for my
ENVIRONMENT that cannot possibly contain anything of value for this situation,
other than the data I already included in the report.
Alright, we are at a standstill here, because I'm unable to do MY work thanks
to this little issue that, if you get your way, will remain unresolved until it
starts affecting more people and then "whoops we didn't get anyone reporting
it! report bugs!"
Am I supposed to return to IceWM in 2019 or what? You guys need a code of
conduct. Your behavior is unacceptable and reflects on the entire project by
proxy. I wouldn't DARE dismiss my users when they report bugs like this. Just
because I'm not programming on the same project as you doesn't make me less of
a programmer.
Even if the bug is somehow not tied to kwin it's still a regression that wasn't
there one version ago. If you want to turn your back and act like nothing is
wrong, that's on you. Don't ask for people to report bugs if you are going to
dismiss them even when they already said three times IT HAPPENS WHEN
COMPOSITING IS ENABLED TOO.
--
You are receiving this mail because:
You are watching all bug changes.
