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 1221691 - [abrt] [faf] gnome-initial-setup: unknown function(): /usr/libexec/gnome-initial-setup killed by 5
Summary: [abrt] [faf] gnome-initial-setup: unknown function(): /usr/libexec/gnome-init...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-initial-setup
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Matthias Clasen
QA Contact: Desktop QE
URL: http://faf-report.itos.redhat.com/rep...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-14 14:52 UTC by Vadim Rutkovsky
Modified: 2015-11-19 08:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 08:28:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2157 0 normal SHIPPED_LIVE control-center bug fix and enhancement update 2015-11-19 08:48:59 UTC

Description Vadim Rutkovsky 2015-05-14 14:52:16 UTC 
Crashed when GDM was stopped when GOA was contacted:

From http://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/desktop-gnome-keyring-RHEL-7.2-2-runtest/lastSuccessfulBuild/artifact/journal.log:

 systemd[1]: Stopped GNOME Display Manager.
 gdm[5413]: GdmServer: Started X server process 5926 - waiting for READY
 gdm[5413]: GdmSimpleSlave: Started X server
 gdm[5413]: GdmDisplayStore: Clearing display store
 gdm[5413]: GdmDisplayStore: Unreffing display: 0x7f3beb00c110
 gnome-session[5440]: (tracker-extract:5714): Tracker-CRITICAL **: Could not start decorator: The connection is closed
 gnome-session[5440]: (tracker-miner-fs:5734): Tracker-CRITICAL **: Couldn't create new Files miner: 'The connection is closed'
 gnome-session[5440]: (gnome-initial-setup:5728): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
 gnome-session[5440]: (gnome-initial-setup:5728): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
 gnome-session[5440]: ** (gnome-initial-setup:5728): ERROR **: Failed to get a GoaClient: Error calling StartServiceByName for org.gnome.OnlineAccounts: The connection is closed
 kernel: traps: gnome-initial-s[5728] trap int3 ip:7fd7e02c68c3 sp:7ffca29684a0 error:0

Report URL: http://faf-report.itos.redhat.com/reports/bthash/e0bb3e228fb5a3d7da330fa2e71fc4f6f08b9968/
Comment 1 Matthias Clasen 2015-05-20 18:18:38 UTC 
Why was gdm stopped ? gnome-initial-setup relies on gdm being around to handle the transition from the login screen to the user session, so running gnome-initial-setup without gdm is not going to work well (unless it is running for an existing user). 

But the error here is just that we fail to contact goadaemon - is it not installed ?
Comment 2 Vadim Rutkovsky 2015-05-21 12:09:19 UTC 
(In reply to Matthias Clasen from comment #1)
> Why was gdm stopped ?

This a teardown procedure for any automated test.

> gnome-initial-setup relies on gdm being around to
> handle the transition from the login screen to the user session, so running
> gnome-initial-setup without gdm is not going to work well (unless it is
> running for an existing user). 

In fact it was running in a proper gdm session (started gdm session with autologin enabled, tests were running for about a minute and then 'systemctl stop gdm' was issued).

> But the error here is just that we fail to contact goadaemon - is it not
> installed ?

It was, I guess it was killed along with the session. This should get a lower priority (users are unlikely to stop gdm during inital-setup), but the crash is still an ugly thing
Comment 3 Matthias Clasen 2015-05-28 21:49:47 UTC 
Pushed a fix upstream.
Comment 6 Vadim Rutkovsky 2015-09-07 10:57:10 UTC 
Verified on gnome-initial-setup-3.14.4-5.el7.x86_64
Comment 8 errata-xmlrpc 2015-11-19 08:28:15 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://rhn.redhat.com/errata/RHBA-2015-2157.html
Note You need to log in before you can comment on or make changes to this bug.