Bug 873783

Summary: attach all the info when creating a "potential duplicate"
Product: [Fedora] Fedora Reporter: Andrey V. Henneberg <andrey.henneberg>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: high    
Version: 17CC: abrt-devel-list, dominick.grift, dvlasenk, dwalsh, iprikryl, jfilak, jmoskovc, kklic, mgrepl, mmilata, mtoman
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e42a684b7cf1370e9fcafa399f99ea2737d66abe84188e5298067935049155a0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-03 16:01:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: type
none
File: hashmarkername none

Description Andrey V. Henneberg 2012-11-06 17:12:48 UTC 
Additional info:
libreport version: 2.0.18
kernel:         3.6.3-1.fc17.i686


Potential duplicate bug: 867620
Comment 1 Andrey V. Henneberg 2012-11-06 17:12:52 UTC 
Created attachment 639468 [details]
File: type
Comment 2 Andrey V. Henneberg 2012-11-06 17:12:54 UTC 
Created attachment 639469 [details]
File: hashmarkername
Comment 3 Daniel Walsh 2012-11-06 18:34:06 UTC 
Why is abrt not giving us the setroubleshoot output.


Is this related to the abrt python plugin?
Comment 4 Jiri Moskovcak 2012-11-06 19:40:46 UTC 
As it says in comment#1:

Potential duplicate bug: 867620

- it's really a duplicate of 867620 and ABRT creates a new bug if the Fedora release is different and somehow it fails to attach the AVC.
Comment 5 Jiri Moskovcak 2012-12-20 12:26:21 UTC 
*** Bug 887747 has been marked as a duplicate of this bug. ***
Comment 6 Miroslav Grepl 2012-12-20 21:34:26 UTC 
Well it should definitely work. I has been testing it and it works for me. I think users do something wrong when they are reporting SELinux issues.
Comment 7 Denys Vlasenko 2013-01-03 16:01:42 UTC 
Starting from version 2.0.19 bugzilla reporter's comment generation is reworked.

Now it is controlled by /etc/libreport/plugins/bugzilla_format*.conf files.

Currently, these files will instruct bugzilla reporter to attach setroubleshoot output, since it will match %multiline wildcard here:

%attach:: -reported_to,-comment,-reason,-event_log,%multiline,\
        -coredump,%binary