|
|
217.
|
|
|
The files that contain your preference settings are currently in use. 
You might be logged in to a session from another computer, and the other login session is using your preference settings files.
You can continue to use the current session, but this might cause temporary problems with the preference settings in the other session.
Do you want to continue? |
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconf-sanity-check.c:322
|
|
|
228.
|
|
|
None of the resolved addresses are writable; saving configuration settings will not be possible
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconf-sources.c:436
|
|
|
232.
|
|
|
Unable to store a value at key '%s', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file %s/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
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconf-sources.c:799
|
|
|
263.
|
|
|
No configuration sources in the source path. Configuration won't be saved; edit %s%s
|
|
|
We want to stay alive but do nothing, because otherwise every
request would result in another failed gconfd being spawned.
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:413
|
|
|
265.
|
|
|
No configuration source addresses successfully resolved. Can't load or store configuration data
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:437
|
|
|
266.
|
|
|
No writable configuration sources successfully resolved. May be unable to save some configuration changes
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:454
|
|
|
272.
|
|
|
Failed to write byte to pipe file descriptor %d so client program may hang: %s
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:974
|
|
|
279.
|
|
|
Failed to open gconfd logfile; won't be able to restore listeners after gconfd shutdown (%s)
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:1764
|
|
|
280.
|
|
|
Failed to close gconfd logfile; data may not have been properly saved (%s)
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:1799
|
|
|
287.
|
|
|
Failed to restore original saved state file that had been moved to '%s': %s
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
../gconf/gconfd.c:1924
|
