| Summary: | Uninstall the used debug info packages after the report was sent | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | s3balon <raad> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
s3balon
2009-12-02 17:09:05 UTC
All the things you requested are already present in the DrKonqi version on KDE SC 4.4 (including an option to automatically install the missing packages in order to get a complete backtrace) However the steps about requiring more information about the crash situation (an explanation) and encouraging the user to search for similar reports can not be removed as it is needed in order to get a good report and to save us (bug triagers and software developers) some time. May be I'm missing something ...? Regards The only thing which could be new could be uninstalling the dbg packages that were installed once the report was sent... but I don't know if that would be useful... If the generated report was useful enough to fix the reported bug by the next update and it will be never happed again , what is the justification of holding the dbg package ? If the generated report was useful enough to fix the reported bug by the next update and it will be never happed again , what is the justification of holding the dbg package ? You could need the same dbg package if the application crashes again (a different crash in the same application).. but well.. we should ensure that doesn't happen too often... :-\ It could be re-downloaded whenever it's needed, what do you think? We could offer the possibility to uninstall the used packages, but stating that they could be needed in the future... then it will be users decision (which could default to "Uninstall").. Reopening.. That is excellent! Regarding your comment #1, is it possible to find a way to simplify the process of finding similar reports ? like automatically showing the most frequent reports! <offtopic>Well.. the duplicates steps was improved in KDE SC 4.4 . It should show better matches, and it should handle "duplicates of duplicates".... Try it on 4.4, and if you can suggest a better idea please open a new bug report (the policy is one report per issue...). Simplying the duplicates process too much could mean more work for us. (we already lack manpower currently)</offtopic> Regards (In reply to comment #6) > It could be re-downloaded whenever it's needed, what do you think? We could offer that option, but this is an overkill for users imho, because debug packages tend to be *very* big. I'll make an example. Let's suppose that you have a crash in plasma (which is very common). In debian, you would have to install at least the following packages: libqt4-dbg: download size 157 MB, installed size 436 MB kdelibs5-dbg: download size 91 MB, installed size 256 MB kdebase-workspace-dbg: download size 69 MB, installed size 195 MB So, you will have to download at least 317 MB every time plasma crashes. I think this is not ok for most users out there... Hmm, I just don't understand why *uninstalling* debug symbols either automatically or optionally can improve the work flow and experience. #1. debug symbols are large. It takes at least a few minutes to download (suppose you have great Internet connection). How does re-downloading those debug symbols each time with extra delay bring better experience than just keeping those debug symbols for reuse next time ? That only take (high) bandwidth into account. What if the user's Internet connection is not fast and paid by the volume of generated data traffic ? Downloading those debug symbols every time is just not one acceptable behavior. #2. Ok, I actually don't need to re-download those debug symbols every time, because my package manager keeps the cache of those packages (/var/cache/apt/archives/ for debian). But you still need to install those big packages onto disk, which means heavy I/O and extra delay. If you automatically uninstall them, then another cycle of heavy IO and delay. Does that provide better experience ? The only benefit of automatically removing debug symbols is saving some disk space. But if you consider #2, then those saved disk space is really not that much since you have to keep the cache. 3 years has passed, yet no one has show real interest in implementing this improvement. Close it. |