https://bugs.kde.org/show_bug.cgi?id=521682
--- Comment #58 from Nabeel <[email protected]> --- (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. Three things: 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. I still need to manually remove the snap backend to get discovered to work again, despite it being already disabled, and it automatically gets reinstalled after a few days. 3rd I think all those issues, whether they're snap related or otherwise should all be rolled into one bug report, because it's not reasonable for back end modules to bring down all of the rest of Discover like this. It shouldn't matter whether it's an issue with snap, or firmware updates, or whatnot... 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. This behavior is the problem, not what's causing it in the backend. If multiple things are causing this behavior in the backend, then that just means that there needs to be a fundamental change with how these backends are handled within Discover, so they can't break Discover in this sort of way, if those backends misbehave. Discover is a fundamental and important part of KDE. When Discover breaks in such a way, any user that doesn't know how to navigate through a terminal, is permanently and irrecoverably stuck. That's not an acceptable failure mode. Without using the terminal, those users will never get updates ever again, including the updates that will fix their problem. Treating this as an issue with those backends, instead of a fundamental issue with Discover, makes Discover fundamentally unreliable and unstable. I understand from a technical perspective why the focus might be on the individual separate back,ends that are causing this issue but the problem isn't that the issue happened, the problem is that the issue was at all possible in the first place. That's where our focus should be. 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. -- You are receiving this mail because: You are watching all bug changes.
