You are not logged in.
Pages: 1
I upgraded gnome today and I tried to run visudo (like I did before gnome 2.24) with gedit (export EDITOR=gedit && sudo -E visudo) and it display this error 5 times:
GConf Error: 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.)
gedit open after, visudo doesnt give me any error.
any idea ?
Offline
None so far, but you should search the forum for "gconf orbit stale nfs locks" and keep an eye on those other threads.
Last edited by byte (2008-10-22 23:08:58)
1000
Offline
I upgraded gnome today and I tried to run visudo (like I did before gnome 2.24) with gedit (export EDITOR=gedit && sudo -E visudo) and it display this error 5 times:
GConf Error: 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.)
gedit open after, visudo doesnt give me any error.
any idea ?
Have you tried restarting?
Archi686 User | Old Screenshots | Old .Configs
Vi veri universum vivus vici.
Offline
None so far, but you should search the forum for "gconf orbit stale nfs locks" and keep an eye on those other threads.
thanks I didnt find another thread before asking
Have you tried restarting?
yes I did the upgrade,restarted and got this error
but I looked at another post it seem its a gnome 2.24 bug and a gnome develloper is looking at it.
Offline
If you're just trying to edit your sudoers file easily [non-vi], you could create a symlink from Vi to Nano. Just delete the symlink when you're done editing.
Offline
Pages: 1