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:
Starting gnome-system-log from a Gnome 3 User session produces error in log file but does not ask for the root password.
Version-Release number of selected component (if applicable):
gnome-system-log-3.9.90-3.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. Start RHEL 7.4 with a user logged in to Gnome 3 session
2. press "Windows" key and type "log"
3. Star the "System Log" tool
Actual results:
no root password request and error in journalctl:
Jul 24 12:50:57 xxxx gnome-system-log.desktop[15359]: Refusing to render service to dead parents.
Jul 24 12:51:01 xxxx tracker-extract[4830]: unable to create file '/run/user/14685/dconf/user': Permission denied. dconf will not work properly.
Expected results:
gnome-system-log
Additional Info:
Starting journalctl from the terminal as user shows the following warning:
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.
but shows my log entries for my user. Would be cool if Gnome System log would do the same, so users can look into issues and error messages more easy.
Comment 2Ray Strode [halfline]
2017-09-08 17:23:41 UTC
*** This bug has been marked as a duplicate of bug 1487248 ***
Description of problem: Starting gnome-system-log from a Gnome 3 User session produces error in log file but does not ask for the root password. Version-Release number of selected component (if applicable): gnome-system-log-3.9.90-3.el7.x86_64 How reproducible: always Steps to Reproduce: 1. Start RHEL 7.4 with a user logged in to Gnome 3 session 2. press "Windows" key and type "log" 3. Star the "System Log" tool Actual results: no root password request and error in journalctl: Jul 24 12:50:57 xxxx gnome-system-log.desktop[15359]: Refusing to render service to dead parents. Jul 24 12:51:01 xxxx tracker-extract[4830]: unable to create file '/run/user/14685/dconf/user': Permission denied. dconf will not work properly. Expected results: gnome-system-log Additional Info: Starting journalctl from the terminal as user shows the following warning: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages. Pass -q to turn off this notice. but shows my log entries for my user. Would be cool if Gnome System log would do the same, so users can look into issues and error messages more easy.