https://bugs.kde.org/show_bug.cgi?id=521682
--- Comment #59 from Nate Graham <[email protected]> --- (In reply to Nabeel from comment #58) > (In reply to Nate Graham from comment #56) > > All of you who are discussing Snap, your bug report is Bug 500513. This is > > about the case where Snap support is NOT enabled. > > I think both those bug reports should be rolled into one. No, because there are two bugs. One affects people using Snap, and goes away when they remove the Snap backend. The other one (this one) is not about that and persists even if you don't have Snap at all. > 1st My bug report was rolled into this one, which is why I've been > continuing comment on this one. > > 2nd Snap backend is not enabled for me, yet this still happens anyway. That means you are affected by both Bug 500513 and this one. > despite it being already disabled, and it automatically gets > reinstalled after a few days. This sounds very bad, but it's not a KDE issue. It would be something coming from the distro's packaging. Please do bring it up with them. > No one cares what's going on in the backend. People care that discover is > hanging on checking for updates. That's the core issue, and we shouldn't > lose sight of that. Clearly. But you're on a technical bug tracker which is for tracking specific technical bugs. Since there are multiple bugs, they need to be tracked separately. > We are all well versed enough to be able to dig ourselves out of this hole > in the terminal. > The users that are now permanently and forever stuck, unable to ever update > again, are the users that do not have a voice in this thread, and are the > users that we should be thinking about when we consider how to solve this > issue. > > We can't have this kind of thing happen again. Definitely not! Feel free to be a part of the solution by helping to fix the issue. And afterwards, you can help make sure it doesn't happen again by adding relevant autotests and integration tests. If you aren't capable of performing those actions, then the next most helpful thing you can do is avoid making too much noise in Bugzilla that distracts and de-motivates the developers (who for Discover are all volunteers!) who *are* capable of resolving the issue. Thanks for understanding! No need to reply unless you have new information that can help developers fix the bug. -- You are receiving this mail because: You are watching all bug changes.
