meld stopped working when run as root
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
meld stopped working when run as root
by Grant Edwards-6
::
Rate this Message:
I used to use meld regularly on different versions of system
config files (that are only readble by root). However, sometime recently meld stopped working when run as root: Traceback (most recent call last): File "/usr/bin/meld", line 90, in <module> meldapp.main() File "//usr/lib/meld/meldapp.py", line 982, in main app = MeldApp() File "//usr/lib/meld/meldapp.py", line 562, in __init__ self.prefs = MeldPreferences() File "//usr/lib/meld/meldapp.py", line 435, in __init__ super(MeldPreferences, self).__init__("/apps/meld", self.defaults) File "//usr/lib/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.) Is there any way to get meld working again for root? What's a "configuration server"? I already build it withough gnome support (Gentoo gnome USE flag is unset). -- Grant Edwards grante Yow! ! The land of the at rising SONY!! visi.com _______________________________________________ meld-list mailing list meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
|
|
Re: meld stopped working when run as root
by Grant Edwards-6
::
Rate this Message:
On 2009-08-14, Grant Edwards <grant.b.edwards@...> wrote:
> I used to use meld regularly on different versions of system > config files (that are only readble by root). However, > sometime recently meld stopped working when run as root: So is using meld as root simply out of the question now? -- Grant Edwards grante Yow! Hello. Just walk at along and try NOT to think visi.com about your INTESTINES being almost FORTY YARDS LONG!! _______________________________________________ meld-list mailing list meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
|
|
Re: meld stopped working when run as root
by Kai Willadsen-2
::
Rate this Message:
2009/10/8 Grant Edwards <grant.b.edwards@...>:
> On 2009-08-14, Grant Edwards <grant.b.edwards@...> wrote: >> I used to use meld regularly on different versions of system >> config files (that are only readble by root). However, >> sometime recently meld stopped working when run as root: > > So is using meld as root simply out of the question now? Sorry - meant to respond to this. There haven't been any changes to Meld that should change running as root. See below. 2009/8/15 Grant Edwards <grant.b.edwards@...>: > Traceback (most recent call last): > File "/usr/bin/meld", line 90, in <module> > meldapp.main() > File "//usr/lib/meld/meldapp.py", line 982, in main > app = MeldApp() > File "//usr/lib/meld/meldapp.py", line 562, in __init__ > self.prefs = MeldPreferences() > File "//usr/lib/meld/meldapp.py", line 435, in __init__ > super(MeldPreferences, self).__init__("/apps/meld", self.defaults) > File "//usr/lib/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.) 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. > Is there any way to get meld working again for root? What's a > "configuration server"? I already build it withough gnome > support (Gentoo gnome USE flag is unset). 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. cheers, Kai _______________________________________________ meld-list mailing list meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
|
|
Re: meld stopped working when run as root
by Grant Edwards-6
::
Rate this Message:
On 2009-10-07, Kai Willadsen <kai.willadsen@...> wrote:
>> On 2009-08-14, Grant Edwards <grant.b.edwards@...> wrote: >>> I used to use meld regularly on different versions of system >>> config files (that are only readble by root). ??However, >>> sometime recently meld stopped working when run as root: > > Sorry - meant to respond to this. There haven't been any changes to > Meld that should change running as root. See below. [...] > I'm guessing you're seeing > https://bugzilla.gnome.org/show_bug.cgi?id=555745 (in gconf) That looks like it might be it. Meld is probably the only GTK program I ever run as root. > though why it only just started happening I have no idea. > Anyway, the 'su -' workaround seems to work. Thanks, I'll try that. > 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. I'll take a look at that as well. -- Grant Edwards grante Yow! I'm meditating on at the FORMALDEHYDE and the visi.com ASBESTOS leaking into my PERSONAL SPACE!! _______________________________________________ meld-list mailing list meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
|
|
Re: meld stopped working when run as root
by Grant Edwards-6
::
Rate this Message:
On 2009-10-07, Kai Willadsen <kai.willadsen@...> 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. -- Grant Edwards grante Yow! Nipples, dimples, at knuckles, NICKLES, visi.com wrinkles, pimples!! _______________________________________________ meld-list mailing list meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
|
|
Re: meld stopped working when run as root
by Grant Edwards-6
::
Rate this Message:
On 2009-12-02, Grant Edwards <grant.b.edwards@...> wrote:
> On 2009-10-07, Kai Willadsen <kai.willadsen@...> 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. -- Grant Edwards grante Yow! Somewhere in DOWNTOWN at BURBANK a prostitute is visi.com OVERCOOKING a LAMB CHOP!! _______________________________________________ meld-list mailing list meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
|
|
Re: meld stopped working when run as root
by Grant Edwards-6
::
Rate this Message:
On 2009-12-02, Grant Edwards <grant.b.edwards@...> wrote:
> On 2009-12-02, Grant Edwards <grant.b.edwards@...> wrote: >> On 2009-10-07, Kai Willadsen <kai.willadsen@...> 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 meld-list@... http://mail.gnome.org/mailman/listinfo/meld-list |
| Free embeddable forum powered by Nabble | Forum Help |
