After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 691612 - meld fails when run as root
meld fails when run as root
Status: RESOLVED DUPLICATE of bug 666136
Product: meld
Classification: Other
Component: filediff
1.7.x
Other FreeBSD
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2013-01-12 15:57 UTC by Yuri
Modified: 2013-01-13 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Yuri 2013-01-12 15:57:37 UTC
Sometimes there is a need to run meld as root when environment is run under the regular user.

I am getting this error, see below.
Maybe, as a workaround, it is better to at least make this a warning.

---error---
Traceback (most recent call last):
  • File "/usr/local/bin/meld", line 154 in <module>
    main()
  • File "/usr/local/bin/meld", line 136 in main
    import meld.meldapp
  • File "/usr/local/lib/meld/meld/meldapp.py", line 216 in <module>
    app = MeldApp()
  • File "/usr/local/lib/meld/meld/meldapp.py", line 113 in __init__
    self.prefs = preferences.MeldPreferences()
  • File "/usr/local/lib/meld/meld/preferences.py", line 259 in __init__
    super(MeldPreferences, self).__init__("/apps/meld", self.defaults)
  • File "/usr/local/lib/meld/meld/util/prefs.py", line 93 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://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

Comment 1 Kai Willadsen 2013-01-13 19:52:36 UTC
This happens because we find the gconf bindings, but can't get to a gconf server. We could fall back to the flat-file in this case, but there's no code to do so. While the actual error may be different, this is basically a dupe of bug 666136, since the underlying problem and fix are the same.

*** This bug has been marked as a duplicate of bug 666136 ***