On 2009-12-02, Grant Edwards <[email protected]> wrote:
> On 2009-12-02, Grant Edwards <[email protected]> wrote:
>> On 2009-10-07, Kai Willadsen <[email protected]> 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
>>
>>> 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.
Running "dbus-uuidgen --ensure" created /var/lib/dbus/machine-id,
so now I can run meld using sudo. It will also work after "su -",
but you have to manually set DISPLAY. Not quite as convenient
as it used to be when it would "just work" after an "su", but
it's progress.
--
Grant Edwards grante Yow! I'm using my X-RAY
at VISION to obtain a rare
visi.com glimpse of the INNER
WORKINGS of this POTATO!!
_______________________________________________
meld-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/meld-list
