Created attachment 185914 [details] discover - crash handler SUMMARY When a KDE app crashes a crash handler opens. There is a moving bar in the background, but it doesn't tell you all that much. The idea is to give more feedback to the user so they know what the crash handler is doing. OBSERVED RESULT The crash handler says that it gathers information. What information? How long will it take? It said something about downloading Debug-Symbols: from where? how large is it? how long will it take? The user does not know and is not told. For me personally it was more about knowing when the process will be done. Yesterday I wanted to go to sleep and this thingy took it's sweet time while I didn't know when it would be finished (is it worth the wait because it's 3 minutes or does it collect a huge amount of data and will take another hour?) EXPECTED RESULT The app should be more verbose what it's doing right now and when it will be finished. SOFTWARE/OS VERSIONS Operating System: KDE neon User Edition KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.14.0-33-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION The crash happened in discover but I guess the crash handler is a universal tool (?). I have no idea where to sort this one in.
Created attachment 185915 [details] discover - crash handler-done What you see is when the process is done, but you don't see any indication of how long this will take.
We don't know how long it will take
(In reply to Harald Sitter from comment #2) > We don't know how long it will take Can there at least be a list of what it has to do, what it's doing and what it has already done? Right now it's just a black box where I can't tell how long it has already been working or how long it will take. I'm willing to help KDE with those reports (and I hope they actually help), but the ordinary user who does not care _why_ they program just crashed would may not leaving the window open, but just close the process. They would may do what I did on Windows when it offered to try to "solve" the problem: It never worked so I always abborted the process. The ordinary is might not willing to spend 15 minutes for the operation to complete if they can't tell from the UI that it might take longer.
We also don't really know what steps need doing until they need doing. That said, the user doesn't need to leave the window open for the automatic submission to run. They only need to have pressed the button.