From: Adam Carter <Adam.Carter@optus.com.au>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] cfg-update with meld fails
Date: Wed, 8 Jul 2009 19:08:19 +1000 [thread overview]
Message-ID: <5602B0BD6D59AE4791BE83104940118D012B49CC00@excprdmbxw002.optus.com.au> (raw)
Ok, I think this problem occurred during the last gnome update. When cfg-update kicks off meld it dies with the error below. Running meld as a user works fine, running say xterm as root works fine but running meld as root fails. Anyone know what's wrong? I googled the error but didn't come up with anything useful.
Traceback (most recent call last):
File "/usr/bin/meld", line 90, in <module>
meldapp.main()
File "//usr/lib64/meld/meldapp.py", line 982, in main
app = MeldApp()
File "//usr/lib64/meld/meldapp.py", line 562, in __init__
self.prefs = MeldPreferences()
File "//usr/lib64/meld/meldapp.py", line 435, in __init__
super(MeldPreferences, self).__init__("/apps/meld", self.defaults)
File "//usr/lib64/meld/prefs.py", line 92, in __init__
self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE)
glib.GError: 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.)
reply other threads:[~2009-07-08 9:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5602B0BD6D59AE4791BE83104940118D012B49CC00@excprdmbxw002.optus.com.au \
--to=adam.carter@optus.com.au \
--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