After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 587765 - Error from gconf when i open a file with gedit with root privileges
Error from gconf when i open a file with gedit with root privileges
Status: RESOLVED DUPLICATE of bug 555745
Product: GConf
Classification: Deprecated
Component: gconf
2.26.x
Other All
: Normal normal
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-04 17:55 UTC by galactic cowboy
Modified: 2009-07-05 10:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description galactic cowboy 2009-07-04 17:55:27 UTC
Please describe the problem:
When i open some file with Gedit with the root privileges (using "su") i see this on gnome-terminal:

Errore di GConf: Contatto col server di configurazione non riuscito; tra le possibili cause la necessità di abilitare il supporto TCP/IP per ORBit o la presenza di un vecchio blocco NFS causato da un crash del sistema. Consultare http://www.gnome.org/projects/gconf/ per ulteriori informazioni (dettagli -  1: Recupero delle connessione alla sessione non riuscito: 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.).


Steps to reproduce:
1. open with gedit some file from the gnome-terminal with root privileges


Actual results:
Error:

Errore di GConf: Contatto col server di configurazione non riuscito; tra le possibili cause la necessità di abilitare il supporto TCP/IP per ORBit o la presenza di un vecchio blocco NFS causato da un crash del sistema. Consultare http://www.gnome.org/projects/gconf/ per ulteriori informazioni (dettagli -  1: Recupero delle connessione alla sessione non riuscito: 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.).


Expected results:
No errors on gnome-terminal.

Does this happen every time?
yes

Other information:
Comment 1 Christian Persch 2009-07-05 10:54:26 UTC
See bug 555745 and https://bugs.freedesktop.org/show_bug.cgi?id=17970 . 



*** This bug has been marked as a duplicate of 555745 ***