Bug 671253

Summary:	Emacs error when started over SSH on NFS
Product:	[Fedora] Fedora	Reporter:	holtz <holtz>
Component:	emacs	Assignee:	Karel Klíč <kklic>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	14	CC:	edavid, jonathan.underwood, kklic, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-27 10:24:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description holtz 2011-01-20 21:23:32 UTC

Description of problem:
We're getting the following error when starting emacs over ssh with X11 forwarding when utilizing NFS.

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Error connecting: Connection refused)

Version-Release number of selected component (if applicable):
emacs-23.2-7.fc14.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure NFS for shared home directories
2. SSH to a different machine on the network (X11 forwarding enabled)
3. run emacs
  
Actual results:
Emacs appears to run fine, but throws the error.

Expected results:
No error.

Comment 1 Erwan David 2011-02-02 07:20:49 UTC

I get same error without NFS, but with SSH and remote display of emacs

Comment 2 Karel Klíč 2011-09-27 10:24:51 UTC

Thank you for the report.

The message says that GConf library failed to contact configuration server. That is probably correct information and it's caused by the server not running the configuration server daemon for given user.

You might want to setup ssh sessions to run per-user desktop daemon(s) on that server, as you run desktop applications from there.

The error message informing user that some functionality is not available because of missing external service seems appropriate to me.

Feel free to reopen this bug if you have some idea how to proceed with this in a  way that requires changes in Emacs.