On Thu, 2010-07-08 at 17:17 +0200, Denys Vlasenko wrote:
abrt-handle-crashdump DIR [PARAMS] Processes given crashdump directory. [Best to implement as shell script, to make it easier to set up custom processing? this way, sosreport, filetransfer/ticketuploader plugins are no longer needed - they can be easily implemented in shell script] STAGE: created / uploaded / collectinfo / report / ...
How to configure abrt-handle-crashdump?
conf file?
# stage [env vars] cmd [params] uploaded abrt-action-get-build_ids uploaded abrt-action-generate-backtrace created abrt-action-upload ftp://user:pass@host/dir created abrt-action-sosreport collectinfo abrt-action-sosreport collectinfo abrt-action-get-build_ids collectinfo abrt-action-debuginfo-install collectinfo FORCE=1 abrt-action-generate-backtrace report abrt-action-bugzilla https://bz-web1-test.devel.redhat.com/ report abrt-action-logger report user_custom_shell_script
Here are some thoughts how we could evolve abrt-handle-crashdump:
This config file can be used as an effective way how to support 3rd party plugins: custom reporters, custom collectinfo steps, custom shell scripts -- whatever a power user or admin wants. It allows a good degree of customization by env. variables and parameters, but it does not allow everything we want to offer to GUI and CLI users on the desktop.
Can you describe what we want to offer to GUI and CLI users? This needs to be described (written down), so far it exists only in our heads.
I was under impression that we want *mostly automated* bug reporting. Seems like you want more like *manual bug reporting* instead. For example, it seems you want reporting to be completely customizable on the user side. This is news to me.
So, what are our goal(s)? Before we can meaningfully discuss the design, we need to discuss what we want to achieve, which use cases do we want to support.
Here's where we can start fishing for use cases - the RFC's we have files against abrt.
Requests to add package-specific data to crash dumps:
606123 abrt should have an easy way to include smolt-profile 531365 [RFE] include SMART snapshot data in all bugs filed against devicekit-disks, palimpsest, libatasmart 539532 RFE: Attach last few lines from ~/.xsession-errors for glib-based apps
Requests to make plugin interactive:
526212 [RFE] Manual pre-check for duplicate bug before reporting to Bugzilla 556755 RFE: please allow bugzilla product/component selection 559536 Can't report third party packages crashes using Bz reporter: fedora bz has no matching component => bug submission fails 560960 Make it more obvious for first-time user where to set up Bz username/pwd 571812 User-experience problems with Bugzilla configuration. 586515 If the user doesn't have a BZ account filled in, the ABRT user experience is really poor 575396 please check for duplicates before prompting for user input 588009 RFE: Don't log bugs for GA versions, when updates exist (or _at least_ warn the user, and note it in the report) 588310 RFE: Check for update before filing bug 592010 ABRT and searching for already open bugs 606241 [FutureFeature] - Test login for Bugzilla in plugin conf
Others:
558429 Abrt doesn't catch repeatable Xorg crashes 574148 abrt failed to deal with X crash 555205 RFE: include "rpm -qf" output for all memory-mapped DSOs 556738 RFE: Use /usr/share/doc/python-devel-2.6*/gdbinit if app is python 557943 RFE: Manually report a bz through abrt 565722 RFE: include errno for all threads in backtraces generated with abrt 565725 RFE: include recent /var/log/messages output of crashed programs 574737 RFE: detect application crashes caused by OOM killer 585039 RFE: abrt-cli command to initiate abrt-download-debuginfo operation 525858 [RFE] Check and remove passwords etc from backtrace 541928 RFE: ability to perform an operation on multiple reports 588170 Abrt never store account information 588209 RFE: add View button into UI 593421 [RFE] "Frustration Button": Extend ABRT to allow user initiation 612468 RFE: support multi-repository environment 573175 RFE - ABRT Package Kit Integration