Re: meld stopped working when run as root

[Kai Willadsen <kai willadsen gmail com>]

2009/12/3 Grant Edwards <grant b edwards gmail com>:
> On 2009-12-02, Grant Edwards <grant b edwards gmail com> wrote:
>> On 2009-10-07, Kai Willadsen <kai willadsen gmail com> wrote:
>>
>>> I'm guessing you're seeing
>>> https://bugzilla.gnome.org/show_bug.cgi?id=555745 (in gconf) though
>>> why it only just started happening I have no idea. Anyway, the 'su -'
>>> workaround seems to work.
>>
>> Using 'su -' produces a different error:
>>
>>   # meld
>>   process 8383: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
>>   See the manual page for dbus-uuidgen to correct this issue.
>>     D-Bus not built with -rdynamic so unable to print a backtrace
>>   Aborted

Meld doesn't explicitly pull in dbus, so I'm guessing that it's being
triggered from gconf? However, the dbus set up is, I think, a deeper
problem.

>>> Unless Gentoo has patched one in, Meld doesn't support a 'no Gnome'
>>> mode. Having said that, if Meld fails to find gconf, it will use
>>> python's configparser configuration backend instead. If you really
>>> don't want gconf at all, you can change the import logic at the end of
>>> prefs.py.
>>
>> Modifying the import logic to not use gconf does work.
>
> Crap.  I posted too soon.  Modifying the import logic only lets
> you start up meld without comparing any files.  As soon as you
> try to compare two files, you get the same D-bus error as
> before.  Still can't use meld as root.

Sorry - there is another gconf import in historyentry.py, around line
183. It should fallback to doing nothing if gconf isn't found, but
since it's installed in your case you'll have to explicitly disable
the import there as well.

cheers,
Kai