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 1627056 - [abrt] [faf] gnome-session: raise(): /usr/libexec/gnome-session-check-accelerated-gles-helper killed by 5
Summary: [abrt] [faf] gnome-session: raise(): /usr/libexec/gnome-session-check-acceler...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-session
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL: https://faf.lab.eng.brq.redhat.com/fa...
Whiteboard:
Depends On:
Blocks: 1636536
TreeView+ depends on / blocked
 
Reported: 2018-09-10 11:03 UTC by Vladimir Benes
Modified: 2019-08-06 12:38 UTC (History)
6 users (show)

Fixed In Version: 7.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1636536 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:37:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2044 0 None None None 2019-08-06 12:38:19 UTC

Description Vladimir Benes 2018-09-10 11:03:22 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: https://faf.lab.eng.brq.redhat.com/faf/reports/bthash/c2fa4c4061319e31fb9806a9cb3b81988f2644b1/

Comment 1 Vladimir Benes 2018-09-10 11:04:15 UTC
seems to be ppc64 and ppc64le only

Comment 3 Ray Strode [halfline] 2018-09-26 20:34:12 UTC
So this crash is the result of the X server failing to start, or perhaps it getting killed shortly after starting. something like that.

It results in gnome-shell accel helper failing to connect to the display, and handling that failure poorly.

This commit should make error recovery more graceful:

         if (!g_option_context_parse (context, &argc, &argv, &error)) {
-                g_error ("Can't parse command line: %s\n", error->message);
+                g_debug ("%s\n", error->message);
                 g_error_free (error);
                 goto out;
         }

vbenes does it happen every login, or was this just something you noticed in the faf reports ?

If so, there could be an X server issue that needs addressing as well.

Comment 4 Ray Strode [halfline] 2018-10-02 14:28:34 UTC
i think this is too late for GA, but i guess we can do it as a 0day

Comment 14 errata-xmlrpc 2019-08-06 12:37:45 UTC
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://access.redhat.com/errata/RHBA-2019:2044


Note You need to log in before you can comment on or make changes to this bug.