# Analyze
EVENT=post-create analyzer=Kerneloops
        # >> instead of > is due to bugzilla.redhat.com/show_bug.cgi?id=854266
        # 'dmesg' file is required by check-oops-for-hw-error
        dmesg >>dmesg
        # Do not fail the event (->do not delete problem dir)
        # if check-oops-for-hw-error exits nonzero:
        {
        abrt-action-check-oops-for-hw-error || true
        } &&
        {
        # run abrt-action-analyze-oops only if check-hw-error didn't create the
        # required files
        if test ! -f uuid -a ! -f duphash; then
             abrt-action-analyze-oops || exit 1
        fi
        } &&
        abrt-action-save-kernel-data


# If you want behavior similar to one provided by kerneloops daemon
# distributed by kerneloops.org - that is, if you want
# oopses to be reported automatically and immediately without
# user interaction, uncomment this line:
#EVENT=post-create analyzer=Kerneloops
        reporter-kerneloops

# Report
#EVENT=report_Kerneloops analyzer=Kerneloops
        reporter-kerneloops

EVENT=report_Bugzilla analyzer=Kerneloops
        reporter-bugzilla -b \
                -F /etc/libreport/plugins/bugzilla_format_kernel.conf

# Send micro report
EVENT=report_uReport analyzer=Kerneloops
        /usr/libexec/abrt-action-ureport

# Update ABRT database after successful report to bugzilla
EVENT=post_report analyzer=Kerneloops
        reporter-ureport -A -B
        exit 0

# Automatic/simple GUI-based kernel oopses reporting will do this:
EVENT=report-gui analyzer=Kerneloops
        report-gtk -- "$DUMP_DIR"

EVENT=report-cli analyzer=Kerneloops
        report-cli -- "$DUMP_DIR"