| Summary: | Bult-in bug reporting system does not work as expected | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Andrei ILIE <andrei.ilie> |
| Component: | general | Assignee: | Dario Andres <andresbajotierra> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot of the bug in action | ||
|
Description
Andrei ILIE
2009-12-15 17:02:57 UTC
Created attachment 39072 [details]
screenshot of the bug in action
Several things:
---
> The bug shold have been processed and sent to KDE team automatically (without
> the user having to log on any web site and write and write and write... )
That would be the perfect situation on a perfect world :)
Currently, we don't have enough people to work on organizing the bug reports, so a 100% automatic system is only going to fill up our databases without letting us properly identify the issues and fix them. I hope you understand that.
We need the user to properly describe the crash situation in order to get a useful bug report.
This fact is not stated clearly on KDE SC 4.3. However I have improved the situation on KDE SC 4.4, when we state that we need certain information or the report will only waste the developers time.
We have also added a proper filter to determine if the information the user can provide is useful for us or not.
---
About the screenshot:
- Problem 1:
Some hints/information about debugging symbols and packages is given at the link "How to create useful good reports" (inside the red square). Some other information is also given in the "Help". Have you read them ? Do you think we should add more information about this step ?
- Problem 2:
If you click yes, the text in the middle gain a red border (just to say "read me")
In KDE SC 4.3, the user must manually read the help and install the missing packages, to finally press the Reload button and hopefully get a better backtrace.
In KDE SC 4.4 we added the posibility to do all this automatically, so the user (using a common GNU/Linux distribution) will only press a button (named "Install missing debug info"..), and the backtrace should get better automagically. That is a good improvement already.
- Problem 3:
That depends on which packages did you needed. I realize that a non-experienced user will have some trouble to recognize the needed packages, even when looking at the help, but that should be improved/fixed on KDE SC 4.4
(little hint, for Plasma crashes you need "kdebase4-workspace-debuginfo"; for most of the KDE apps' crashes you need "kdelibs5-debuginfo" too)
I don't think this is an "important problem" as "reporting a crash" is not a common task (I think), even when KDE applications crash a lot. In any case, and as I just stated, most of this issues will be fixed on KDE SC 4.4
- Do you think of any other problem that should be fixed? (sorry, we can't change the texts because of the "string freeze" policy before the KDE SC 4.4 release)
- Would you like to discuss some other thing?
Regards, and thank you for the feedback.
Hello,
About my report, the KDE's 4.3 Crash Handler Alert is somewhat misleading: I expected that hitting the "Yes" button will cause the system to initiate something to be installed, but nothing happened. The message in the alert is unclear to the average user.
Thank you for your explanations and hopefully the bug reporting system of KDE becomes more clear and user-friendly in the next stable release (KDE 4.4) because, in my opinion, the bug reporting system is truly an important matter (it is important that ***everyone*** should be able to easily send quality feedback to help further improve this good product).
PS:
1. I've used yast from opensuse to try installing those two packages ("kdebase4-workspace-debuginfo", "kdelibs5-debuginfo") but with no luck - they do not exist (under this name, at least)
2. MS Windows (98, Me, XP, etc) has a ***very*** useful feature named "Tile windows vertically | horizontally". I think you know what i'm talking about. Do you think we're going to enjoy that on KDE (base) in the next 10 years or so ? :)
Thanks for your time and keep up the good work !
I just fixed a bug to improve the behavior on this situation About the packages I mentioned: take a look at this page: http://software.opensuse.org/search?q=kdebase4-workspace-debuginfo http://software.opensuse.org/search?q=kdelibs5-debuginfo About window tiling, I think some related features were implemented but I can't be sure. It is out of my scope. May be you could ask at http://forum.kde.org/ Thanks for the feedback. |