#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment (by duffy):
Hi!
So I'm trying to get abrt running on my F11 system but it just doesn't load. I tried to install it from the rawhide repo but it won't install because of a weird rpm error "rpmlib(PayloadIsXz) is needed by abrt- libs-0.0.7.1-1.fc12.x86_64"
I would like to get a feel for how the app works right now, any ideas on how I could run it?
Other than that I have some specific questions:
- How is it launched? It is launched from a desktop menu primarily? - Does it have an applet? - Does it pop-up a dialog during an application crash? - How does it interact with Bug Buddy? - What kind of user information is being collected to enable the bug report? Does the user need a Bugzilla user id / password? Does the user need to fill anything out or is the intention that just the backtrace gets sent and the user doesn't need to input anything?
Are there any specific applications you're trying to model it against? E.g., I think the kernel oops reporting tool is nice, because it almost never gets in my way, it just does its job and doesn't need to be touched or configured, it just works. Rather than have a separate GUI with a separate menu item for this, you might want to consider building a preferences capplet for it for the system menu, and just letting the users modify whatever information is there (email address, bugzilla log, whatever) but have sane defaults, and maybe have a tab where they can look up the status of the bugs they already reported (I wish that kernel oops had this.)
Let me know what you think.