Re: Support for DBUS-less mode.

[Gilboa Davara <gilboad gmail com>]

On Tue, Mar 19, 2013 at 11:36 PM, Kai Willadsen <kai willadsen gmail com> wrote:
> On 17 March 2013 20:12, Gilboa Davara <gilboad gmail com> wrote:
> > On Sat, Mar 16, 2013 at 10:07 PM, Kai Willadsen <kai willadsen gmail com>
> > wrote:
> > > On 16 March 2013 14:57, Gilboa Davara <gilboad gmail com> wrote:
> > > > Hello,
> > > >
> > > > When trying to used meld to compare files as root, I'm getting
> > > > exceptions
> > > > due to meld being unable to connect to DBUS (access denied).
> > > >
> > > > (meld:29000): GConf-WARNING **: Client failed to connect to the D-BUS
> > > > daemon:
> > > > 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.
> > > > Traceback (most recent call last):
> > > >   File "/usr/bin/meld", line 154, in <module>
> > > >     main()
> > > >   File "/usr/bin/meld", line 136, in main
> > > >     import meld.meldapp
> > > >   File "/usr/share/meld/meld/meldapp.py", line 216, in <module>
> > > >     app = MeldApp()
> > > >   File "/usr/share/meld/meld/meldapp.py", line 113, in __init__
> > > >     self.prefs = preferences.MeldPreferences()
> > > >   File "/usr/share/meld/meld/preferences.py", line 259, in __init__
> > > >     super(MeldPreferences, self).__init__("/apps/meld", self.defaults)
> > > >   File "/usr/share/meld/meld/util/prefs.py", line 93, in __init__
> > > >     self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE)
> > > > glib.GError: No D-BUS daemon running
> > > >
> > > > Any chance of making meld simply disable dbus support when dbus is
> > > > unavailable?
> > >
> > > This is actually gconf, not Meld. Meld *also* has dbus support, but
> > > that should fail gracefully if we can't connect. We also have a
> > > fallback for gconf support, but right now it only works if you don't
> > > have gconf installed; if it's installed but can't connect, then it
> > > blows up as above.
> > >
> > > It probably wouldn't be too hard to make that fallback depend on
> > > actual gconf viability rather than presence, but I haven't really
> > > looked into it.
> > >
> > > cheers,
> > >
> > > Kai
> >
> >
> > OK, thanks.
> > You want me to open a BZ?
>
> Turns out we already had one:
>     https://bugzilla.gnome.org/show_bug.cgi?id=666136
>
> Reading through that, it looks like we can't sanely handle this since
> gconf error handling isn't bound in Python. For me this goes on the
> list of things that will change/get fixes by a Gtk3 port... one day.
>
> cheers,
> Kai

Hi,

I see that gconf can be safely disabled by editing the code.
Can this be done (in future versions) via a command line switch?

- Gilboa