https://bugs.kde.org/show_bug.cgi?id=431561
--- Comment #2 from Harald Sitter <sit...@kde.org> --- It's not trivial I should add. >From a bit of browsing through the source there isn't a good architecture in place to implement this. Problem #1 is that traces aren't fetched until the user either goes to the developer tab or clicks report bug meaning we can't tell the user right away that the crash is unfortunate but out of the hands of the application. Then 'report bug' has the additional complication that it wants to ask the user questions before getting the trace meaning the user will get annoyed because the provided ultimately useless info. And to top it all off there is no notion that a trace/report might be entirely discard based anything so there's also no UI backing. Realistically I guess we could get away with solving this in the UI exclusively by checking the combined trace output against the '...connection broke...' string and if applicable inject a final dialog page explaining that the crash is caused elsewhere and cannot be filed. This will only be possible once the trace is fetched on the tracing page though. -- You are receiving this mail because: You are watching all bug changes.
