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.
Description of problem:
abrt-cli list prompts for root user password even after setting PrivateReports variable to 'no' in /etc/abrt/abrt.conf
$ abrt-cli list
PrivateReports is enabled. Only "root" can see the problems detected by ABRT.
Do you wan to run abrt-cli-root? [y/N]"
With disabling PrivateReports, even root user is prompted with this message.
# abrt-cli list
PrivateReports is enabled. Only "root" can see the problems detected by ABRT.
Do you wan to run abrt-cli-root? [y/N]
Now, if I enable PrivateReports [PrivateReports = yes], normal users are prompted with this message (as expected). But if I reply with 'N', it lists out the newly created Problem Directory of that user.
===============================
$ tail -2 /etc/abrt/abrt.conf
#
PrivateReports = yes
$ abrt-cli list
PrivateReports is enabled. Only "root" can see the problems detected by ABRT.
Do you wan to run abrt-cli-root? [y/N] N
@0
Directory: /var/spool/abrt/ccpp-2016-03-16-19:39:05-24789
count: 1
executable: /bin/sleep
package: coreutils-8.4-37.el6
time: Wed 16 Mar 2016 07:39:05 PM IST
uid: 500
Run 'abrt-cli report /var/spool/abrt/ccpp-2016-03-16-19:39:05-24789' for creating a case in Red Hat Customer Portal
The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
===============================
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.7
abrt-2.0.8-34.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Disable PrivateReports. Set 'PrivateReports = no' in /etc/abrt/abrt.conf
2. # service abrtd restart
3. $ abrt-cli list // As a user,
Actual results:
$ abrt-cli list
PrivateReports is enabled. Only "root" can see the problems detected by ABRT.
Do you wan to run abrt-cli-root? [y/N]"
Expected results:
It should list out the user's Problem directories with prompting for root password.
Additional info:
A workaround is If replied with "N" to the question, it list's out the users's directories.
Correcting the Expected Results part in Description :
Expected results:
It should list out the user's Problem directories without prompting for root password, if PrivateReports is set to 'no'.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0768.html