Additional info: libreport version: 2.0.18 kernel: 3.6.3-1.fc17.i686 Potential duplicate bug: 867620
Created attachment 639468 [details] File: type
Created attachment 639469 [details] File: hashmarkername
Why is abrt not giving us the setroubleshoot output. Is this related to the abrt python plugin?
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.
*** Bug 887747 has been marked as a duplicate of this bug. ***
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.
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