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.
Bug 1474357 - error messages while starting gnome-system-log via terminal
Summary: error messages while starting gnome-system-log via terminal
Keywords:
Status: CLOSED DUPLICATE of bug 1487248
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-system-log
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 12:50 UTC by Oliver Ilian
Modified: 2018-01-22 15:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-22 15:25:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Oliver Ilian 2017-07-24 12:50:45 UTC 
Description of problem:
When you start gnome-system-log via terminal, a lot of critical errors show up

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 gnome-system-log

Actual results:
** (logview:30435): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-11qk55G5tS: Connection refused
Gtk-Message: Failed to load module "unity-gtk-module"
Gtk-Message: Failed to load module "unity-gtk-module"

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): GLib-GIO-CRITICAL **: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed

(logview:30435): Gtk-CRITICAL **: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed

(logview:30435): Gtk-WARNING **: Allocating size to GtkScrolledWindow 0xbe6300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

Expected results:
no errors :D
Comment 2 Josh 2018-01-22 15:19:22 UTC 
I came across this bug when investigating an issue with our CentOS servers after a recent update.  I see the bug is still listed as new, is there any progress on this?

Recently upgraded Centos from v7.3.1 to v7.4.1708 and am having issues opening a couple applications.  One of them was System Log from the GUI.  When launching from the terminal I get the errors above.

Thank you,
Comment 3 Ray Strode [halfline] 2018-01-22 15:25:41 UTC 
This issue is currently, tentatively scheduled to be addressed in the next Red Hat Enterprise Linux 7 synchronous update.

*** This bug has been marked as a duplicate of bug 1487248 ***
Note You need to log in before you can comment on or make changes to this bug.