Summary: | gnome-extra/gconf-editor-2.24.1 shows no entry and gives error when executed by root | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabiano Francesconi <fabiano.francesconi> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | rose |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fabiano Francesconi
2009-04-03 09:53:01 UTC
Which entry would you expect it to show you ? Those of the root user ? Then you should start a gconfd-2 for root. If you want to see the users gconf values you might be missing some environment variables from user environment. (In reply to comment #1) > Which entry would you expect it to show you ? Those of the root user ? Then you > should start a gconfd-2 for root. If you want to see the users gconf values you > might be missing some environment variables from user environment. > In example meld use it to add a dir. Cfg-update uses meld to compare two conf files but this is the output when running meld by root: File "//usr/lib/meld/prefs.py", line 91, in __init__ self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE) glib.GError: Contatto col server di configurazione fallito; tra le possibili cause la necessità di abilitare il supporto a TCP/IP per ORBit o la presenza di un vecchio lock NFS a causa di un crash di sistema. Consultare http://www.gnome.org/projects/gconf/ per ulteriori informazioni (Dettagli - 1: Recupero delle connessione alla sessione fallito: 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 guess something is wrong here, don't know what. I have no reason to use gconftool-2 from root. The only one is meld. But I can't understand why before the upgrade it was working like a charm and now it's not. because things changed. try unsetting DBUS_SESSION or set it to the same value you are using with your user and see if it helps. (In reply to comment #3) > because things changed. try unsetting DBUS_SESSION or set it to the same value > you are using with your user and see if it helps. > I've only DBUS_SESSION_BUS_ADDRESS and it's set to the same value for both users. I guess DBUS_SESSION is already unset for both users. then try unsetting DBUS_SESSION_BUS_ADDRESS... (In reply to comment #5) > then try unsetting DBUS_SESSION_BUS_ADDRESS... > it does work now. What should I do to make it permanently? either use su - or sudo which cleans your environment variables by default. I'm closing invalid because this is not a bug in the program it tries to access the bus, get's a no which triggers the error message you are seeing. *** Bug 347177 has been marked as a duplicate of this bug. *** |