Bug 1221691

Summary:	[abrt] [faf] gnome-initial-setup: unknown function(): /usr/libexec/gnome-initial-setup killed by 5
Product:	Red Hat Enterprise Linux 7	Reporter:	Vadim Rutkovsky <vrutkovs>
Component:	gnome-initial-setup	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://faf-report.itos.redhat.com/reports/bthash/e0bb3e228fb5a3d7da330fa2e71fc4f6f08b9968/
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 08:28:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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