Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 480227 [details]
screenshot

Description of problem:
I've come across SELinux denial and when I try to report it using SELinux troubleshooter a dialog appears. I believe this dialog comes from report.


From the available options: local, GLS, scp, etc. I selected local.

I was presented with a dialog to enter directory path where to save the bug report. This dialog looks like in the attached screenshot. 


The problem is that there's no indication that the path should be an absolute path. At first I thought that this was a relative path to the user's home directory so I entered 'test' which failed with permission denied. Then I entered '/home/atodorov/test' and the directory was successfully created.

Version-Release number of selected component (if applicable):
report-0.18-7.el6

How reproducible:
Always

Steps to Reproduce:
1. Try to report some bug. For example using SELinux troubleshooter.
2. Select to save the report in a local file.
3. 
  
Actual results:
User is presented with dialog asking for directory path but there is no explanation that this path should be an absolute path.

Expected results:
There is explanation what type of path is this.

Additional info:
See screenshot.

Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

I tried reporting an issue with abrt-gui on latest 6.2 and selected the Logger plugin. The report was saved locally in /tmp/abrt.log and the above UI was not present. This bug can't be reproduced with libreport.