public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: gconf problems
Date: Mon, 25 May 2009 14:51:48 -0700	[thread overview]
Message-ID: <gvf3rl$cjv$1@ger.gmane.org> (raw)
In-Reply-To: <1243223582.3901.8.camel@bunyip.localdomain>

W.Kenworthy wrote:
> I started getting these errors recently from a number of systems, as
> well as failures in operation.  The cause appears to be scripts/programs
> running as root trying to contact the user gconf daemon.  This is
> "stupid" so how can I work around it.  One case I am trying to fix is
> hibernate scripts resetting the background on a laptop before it shuts
> down - fails.  Another is killing evolution from root when it dies, wont
> exit etc.
>
> Billk
>
> 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://www.gnome.org/projects/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.)

Using the tried-and-true SWAG method, my only idea is that maybe your
gnome-session is not being started with dbus-launch.  I notice that
/etc/X11/Sessions/Gnome (used by gdm) was recently changed to remove the
use of dbus-launch, and I'm inclined to think that was a 'misteak'.

How are your gnome-sessions being started?




      reply	other threads:[~2009-05-25 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25  3:53 [gentoo-user] gconf problems W.Kenworthy
2009-05-25 21:51 ` walt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gvf3rl$cjv$1@ger.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox