https://bugs.kde.org/show_bug.cgi?id=469445
--- Comment #28 from pallaswept <pallasw...@proton.me> --- (In reply to Oliver Beard from comment #27) > (In reply to Nikolas Spiridakis from comment #26) > > I don't want to be rude but this does not fix the core problem. > > The goal is to resolve the slowdown and crashing in 5.27. It's quite likely > that the core issue will be addressed for Plasma 6, but such major work > would not be brought to 5.27. That seems very sensible to me.... but if that is the intention then this case should not be marked as resolved and fixed until it is actually resolved and fixed, which it isn't. Perhaps it would be preferable to create a new bug report for work on Plasma 6 and resolve this case with reference to that new bug. But leaving a bug existing with knowledge of it and no bug open basically means "we hope someone remembers to get back to this or we're going to find out when it comes back and bites us in the butt later on". Please don't do stuff that's going to create more problems in the future. I don't want it to come back and bite you or I later on. We all want the KDE developers' lives to be easier, and this is not the means to that end. I'll leave it to somebody in a position of authority to reopen this case or create a new one or whatever means best ensures that this isn't forgotten. Anyway enough discussion of the correct process for resolving cases. I'll take off my ITIL hat and put my end-user hat back on now. Thank you very much for providing us all with this workaround in the meantime, KDE is amazing with thanks to people like you and I miss it when it doesn't load :) Now I can close my config file I've been nervously checking every day, and relax, and it's thanks to you, Olivier, Nate, especially Harald for writing the code nice one mate!.... and anybody else I might have missed. Greatly appreciated! <3 -- You are receiving this mail because: You are watching all bug changes.
