--- Begin Message ---
-----Messaggio originale-----
Dear Mr. Sebastien Bacher,
I missed to substitute a variable, the english message is:
Unable to store a value at key '/apps/nautilus/preferences_version', as the
configuration server has no writable databases. There are some common causes of
this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain
any databases or wasn't found 2) somehow we mistakenly created two gconfd
processes 3) your operating system is misconfigured so NFS file locking doesn't
work in your home directory or 4) your NFS client machine crashed and didn't
properly notify the server on reboot that file locks should be dropped. If you
have two gconfd processes (or had two at the time the second was launched),
logging out, killing all copies of gconfd, and logging back in may help. If you
have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you
attempted to use GConf from two machines at once, and ORBit still has its
default configuration that prevents remote CORBA connections - put
"ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details
on problems gconfd encountered. There can only be one gconfd per home
directory, and it must own a lockfile in ~/.gconfd and also lockfiles in
individual storage locations such as ~/.gconf
Patrick
> -----Messaggio originale-----
> Da: Sebastien Bacher [mailto:[EMAIL PROTECTED]
> Inviato: venerd́ 4 febbraio 2005 12.11
> A: [EMAIL PROTECTED]; Patrick Zanon - Isolcell Italia S.p.A.
> Cc: [EMAIL PROTECTED]
> Oggetto: Re: Bug#293319: gconf2: gconf fail to store
> information into/apps/nautilus/preferences_version/
>
> severity 293319 important
> thanks
>
> I'm changing the severity to important since it's not an issue for all
> the users.
>
>
> > file di lock ~/gconfd ed ulteriori file di lock in posizioni di
> > immagazzinamento dati individuali come ~/.gconf
>
> Hi,
>
> Could you provide an english version of the message ?
>
>
>
> Cheers,
>
> Sebastien Bacher
>
>
>
--- End Message ---
