GNU bug report logs - #7249
GConf errors when emacs is launched as root via "su"

Previous Next

Package: emacs;

Reported by: Rob Browning <rlb <at> defaultvalue.org>

Date: Wed, 20 Oct 2010 03:45:03 UTC

Severity: normal

Done: Jan Djärv <jan.h.d <at> swipnet.se>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 7249 in the body.
You can then email your comments to 7249 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#7249; Package emacs. (Wed, 20 Oct 2010 03:45:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rob Browning <rlb <at> defaultvalue.org>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Wed, 20 Oct 2010 03:45:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Rob Browning <rlb <at> defaultvalue.org>
To: bug-gnu-emacs <at> gnu.org
Cc: Vincent Lefevre <vincent <at> vinc17.net>, 595036 <at> bugs.debian.org,
	595036-forwarded <at> bugs.debian.org
Subject: GConf errors when emacs is launched as root via "su"
Date: Tue, 19 Oct 2010 22:39:40 -0500
Launching an emacs built with gconf support as root via "su" (not "su
-"), produces this error:

  # emacs --version
  GNU Emacs 23.2.1
  Copyright (C) 2010 Free Software Foundation, Inc.
  GNU Emacs comes with ABSOLUTELY NO WARRANTY.
  You may redistribute copies of Emacs
  under the terms of the GNU General Public License.
  For more information about these matters, see the file named COPYING.

  # emacs -Q
  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: Did not receive a reply. Possible causes
  include: the remote application did not send a reply, the message bus
  security policy blocked the reply, the reply timeout expired, or the
  network connection was broken.)

Is this the expected behavior?

The original report can be found here:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595036

(If possible, please maintain the 595036-forwarded <at> bugs.debian.org
 address in any replies.)

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4




Reply sent to Jan Djärv <jan.h.d <at> swipnet.se>:
You have taken responsibility. (Wed, 20 Oct 2010 06:06:02 GMT) Full text and rfc822 format available.

Notification sent to Rob Browning <rlb <at> defaultvalue.org>:
bug acknowledged by developer. (Wed, 20 Oct 2010 06:06:02 GMT) Full text and rfc822 format available.

Message #10 received at 7249-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: Rob Browning <rlb <at> defaultvalue.org>
Cc: Vincent Lefevre <vincent <at> vinc17.net>, 7249-done <at> debbugs.gnu.org,
	595036 <at> bugs.debian.org, 595036-forwarded <at> bugs.debian.org
Subject: Re: bug#7249: GConf errors when emacs is launched as root via "su"
Date: Wed, 20 Oct 2010 08:09:59 +0200
2010-10-20 05:39, Rob Browning skrev:
>
> Launching an emacs built with gconf support as root via "su" (not "su
> -"), produces this error:
>
>    # emacs --version
>    GNU Emacs 23.2.1
>    Copyright (C) 2010 Free Software Foundation, Inc.
>    GNU Emacs comes with ABSOLUTELY NO WARRANTY.
>    You may redistribute copies of Emacs
>    under the terms of the GNU General Public License.
>    For more information about these matters, see the file named COPYING.
>
>    # emacs -Q
>    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: Did not receive a reply. Possible causes
>    include: the remote application did not send a reply, the message bus
>    security policy blocked the reply, the reply timeout expired, or the
>    network connection was broken.)
>
> Is this the expected behavior?
>

I think it is.  It is a GConf limitation/bug.  su followed by for example 
gedit or gnome-help gives the same error.  A bug report to GConf might be in 
order.

	Jan D.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 17 Nov 2010 12:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 14 years and 280 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.