https://bugs.kde.org/show_bug.cgi?id=508912
--- Comment #6 from Nate Graham <[email protected]> --- > you can also try to work on finding out how to reproduce it We can (sometimes, maybe), but frankly it's a waste of our time. We're the ones who can *fix* issues, which is a more difficult and exotic skill, so it makes sense for us to spend more of our time doing that. You can make that possible by reporting issues that are in an actionable state, which minimizes the amount of time we have to spend investigating. https://community.kde.org/Troubleshooting explains all this. It's just how bug reporting/triaging/fixing works. You report an actionable issue, we fix it. If you report "something randomly happens for no reason", it's a waste of our time. You might be tempted to say "well, figuring out the precise cause is a waste of my time, too". If that's the way you feel, you can save everyone a lot of time by not reporting such bugs in the first place, or only doing so once they're in an actionable state — that is to say, when you can reproduce them and won't be tempted to add "randomly" and "for no reason" in the title. -- You are receiving this mail because: You are watching all bug changes.
