Every time I run gedit from the Gnome terminal, I get a long string of repeated error messages like this:
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 GConf configuration system 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 then opens and proceeds to work fine but it’s annoying. Any ideas?
So do I in fedora 10 or my SUSE 11.1 Gnome VM.
Seems to be the norm.
Don’t let it bother you. There are far more important things to be concerned about.
I’m not losing any sleep over it, though it is annoying when it wipes out the command history. Just wondered if using an alternative terminal and/or text editor would make any difference?
Every GUI app I ever run seems to dump garbage to my shell if I run it
from there. Currently I use ‘konsole’ (despite running in Gnome
primarily) and have my histories set to unlimited, which is really handy
at times. So it takes some space… I’ve never had a problem with that
being used temporarily.
Good luck.
gminnerup wrote:
> Now Vi would give me sleepless nights :-). Does using nano get rid of
> the bove error messages? Would be worth considering then.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
bah… apparently you haven’t learned vi. Take a few minutes… you
won’t regret it if you give it a chance:
Run:
vimtutor
Good luck.
Confuseling wrote:
> ab@novell.com;1972821 Wrote:
>> … but vi is superior.
>> …
>>
>
> Yeah, or you could just rip the keyboard out and tap machine code
> directly into the CPU’s pins using an electrician’s screwdriver.
>
>
>
> Try nano.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
There’s a story about the early UNIX vi manual pages, by way of encouragement to those disgusted at the confusing and arbitrary UI, saying; “Try emacs and you’ll feel better”, and in the emacs manual pages, by way of encouragement to those disgusted at the confusing and arbitrary UI, saying; “Try vi and you’ll feel better.”
Yes, that sounds about right. I don’t think either is really that bad…
you just have to be able to understand there is more to manipulating text
than typing on the screen to use either. If you are just typing two
lines then nano is great, but if you ever have to actually edit a file you
need an editor that isn’t garbage. ‘vi’ may not be the one to go with but
it definitely can do the job when it comes to advanced tasks. I think
I’ll bow out after this comment (and your possible reply) unless a
response is requested… I don’t want to get too tied up in a
multi-decade flame war.
Good luck.
Confuseling wrote:
> There’s a story about the early UNIX vi manual pages, by way of
> encouragement to those disgusted at the confusing and arbitrary UI,
> saying; “Try emacs and you’ll feel better”, and in the emacs manual
> pages, by way of encouragement to those disgusted at the confusing and
> arbitrary UI, saying; “Try vi and you’ll feel better.”
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
No flame-bait - that was all intended in good humour. And I fully recognise the power of text editors like vi and emacs, once you understand how to use them. I suppose they’re of a piece with bash itself - in no way designed to be intuitive, but very efficient for the expert.
For now, I think I’ll stick to nano - and my recommendation extends only so far as telling newbies like myself to give it a try.
I have this problem too at the moment. Gconf-editor doesn’t load correctly either, says the same error about stale nfs.
I had a problem with stale nfs a while back too, I found a command that I cannot find again. The command finds and executes a rm on some files. It completely fixed this problem.
I too have a long list of errors/warnings when I start gedit from console, but only when I start it as root (su), no problem when started as regular user.
As Gedit is working anyway, a quick workaround to avoid this output is to suppress it.
