https://bugs.kde.org/show_bug.cgi?id=508868
--- Comment #2 from Jens <[email protected]> --- This bug report was not so much about the crash (I'll investigate anyway though), but about the loop. If an app crashes upon startup, there should be some deescalation strategy so that it doesn't get stuck in a crash loop and make the machine unusable. Ideally, the deescalation strategy could involve a "safe mode" startup of some kind. In the case of discover, the crash may be related to one or more package sources (just guessing) so Discover could detect it crashed (twice or 3x) and then offer to disable some or all package sources on the next start, or return to the default packages sources (temporarily). In any case, it should not restart-crash-restart-crash forever - regardless of the actual crash reason. -- You are receiving this mail because: You are watching all bug changes.
