Summary: | When the information length is not enough, DrKonqi should explain why | ||
---|---|---|---|
Product: | [Applications] drkonqi | Reporter: | rosenfield.albert |
Component: | general | Assignee: | Dario Andres <andresbajotierra> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | andresbajotierra, mail |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
rosenfield.albert
2011-03-17 10:44:28 UTC
1) You are missing debug symbols (which are needed to have a complete backtrace). For that backtrace you would need to install the following packages: "kdelibs-dbg" , "kdebase-workspace-dbg", "libqt4-dbg" 2) The crash you reported is alredy fixed in KDE SC 4.6.0 and later: bug 241562 3) We don't use bug reports for statistics. We receive a lot of them already and we lack manpower even to organize them. So there is even less manpower to process the reports and fix the real bugs.... We needed a way to filter some reports out (those with incomplete backtrace, or not long enough descriptions) We can't accept reports with some kind of context information. So if we want a straight-forward reporting process we need lots of people to process that information later. 4) There are different stages when the reporting assistant prompts for information and later tells you that it is not enought. After you fill the initial checkboxes and the backtrace is generates, the dialog tells you (In the "conclusions" page) if it is worth reporting or not; and it *explains* why. If it is worth reporting and you keep going, then you have to add some context information; in this step the ammount of information you need to enter is proportional to the quality of the backtrace. Example: - If the backtrace is perfect, you need to enter a minimal ammount of characters - If the backtrace is mostly missing or incomplete, you need to enter more information. Currently the limits are based on characters ammount because we didn't implement other smarter way to detect if the user information is useful or just random characters without sense... or whatever. I guess we could try to explain that in the dialog itself. I'm sorry that you lost part of your time and got mad at us. Look at the good side: this crash is already fixed. Additionally, DrKonqi on KDE SC 4.7 will show you (in the duplicates page) which bugs are already fixed, and in which version. So in this case you will see the duplicates that are fixed for "KDE SC 4.6.0", and considering you are using 4.5.1, you will avoid reporting the issue over again. I hope that explains the situation better. And if you have some other ideas on how to improve the DrKonqi workflow or improve the "friendliness" of the interface, without generating more work for the KDE bug triagers and developers, you are welcome to tell us about them. Regards DarĂo A. (former DrKonqi developer) In 3) it should be "We can't accept reports withOUT some kind of context information." Also, about the minimal required information length and the backtrace usefulness: If a backtrace is incomplete, the developers can't really look into it to check what happened, or what was the state of the components of the application, or where the error did come from; that is why a more helpful/long explanation is needed: in order to try to "reproduce"(repeat) the issue themselves and debug the application Simple proposed patch: https://git.reviewboard.kde.org/r/101203 Git commit ca664d7e584c5e6561a0637ab5507a5071b95149 by George Kiagiadakis, on behalf of Dario Andres Rodriguez. Committed on 29/04/2011 at 14:14. Pushed by gkiagia into branch 'master'. Add more explanations about why DrKonqi requires certain amount of characters in the bug description. Tells the user that the required information is proportional to other information, such as the backtrace or the reproducibility rate. Also, check and tell the user if he/she has previously selected that they could provide some contextual information. Additionally add some line breaks to make it easier to read. REVIEW: 101203 BUG: 268734 M +16 -2 drkonqi/reportassistantpages_bugzilla.cpp http://commits.kde.org/kde-runtime/ca664d7e584c5e6561a0637ab5507a5071b95149 |