lockfile gconf freebsd problem

T

triplesquarednine

hey everyone,

i don't know if anyone has encountered this issue b4,

but i am using gnome in freebsd, and gconf seems to be corrupted and not working properly..

basically i am getting an error where gconf is broken due to an improper shutdown. apparently i need to fix my lockfile??

i was directed to gconf on the web, however, all they refer to
on their site is fixing it in redhat 8, which doesn't seem to apply to BSD(and the info seems quite out of date!).

i am currently re-installing as i got so frustrated, and being as this isn't a production machine, i chose to trry a clean install. however, i figure this problem might be encountered again, so i am curious as what to do or what tools i need to
fix this in the future...

if anyone has any knowledge of this i would love to
here from you!
thanx
 
Can you post the error message?
Is this happening only with your user? What creating a new one?
 
ale said:
Can you post the error message?
Is this happening only with your user? What creating a new one?
Click to expand...


i am trying to reproduce the error, but can't remember how it came up the first time...

i can say that it had/has to do with nfs-lock files...
i think it may also be interfering with my ability to use adminstrative things inside of gnome...

...everything is greyed out, ie: if i open /desktop/system/adminstration/users and groups
i cannot "unlock" or change anything, just look..

as soon as i can reproduce the error i will post it here..
thank you for you reply..

:)
 
ha!

i used gconftool and got the error message, or a very similar one:

NinesInRows# gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true

Error setting value: 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://projects.gnome.org/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.)

this was used as "root". gives the same message as "user"..

any ideas???
 
Can you try going into single user mode using # shutdown now from a tty and look what's in /tmp and /var/tmp?

What about the 2nd question in my previous post?
 
hey ale,

i've gotten around this problem by using gconf-editer/configuration editor...

however, say i decide that i want to use gedit to modify a text file or xorg.conf or something like that, that error message will
pop up over and over again...but!!

i can still edit the file, so i don't know if it's really causing me problems really...weird...

***your second question being: just in my user account???
if so, nope, in any account...i haven't setup a new user, but i will try that and see if it's the same(assumptions are bad, but i would assume so...i'll let you know!)

thanx again :)
 
You must log in or register to reply here.
Back
Top