-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vincent Untz wrote:
Le dimanche 26 octobre 2008, à 12:36 +0100, Carlos E. R. a écrit :
Vincent Untz wrote:
No, gconf does not start. I already said that. (I guess you mean gconf-editor, and not gconf) Of course, then I would have said "command not found".
Saying "gconf does not start" implies for me that the gconf daemon does not start, and not gconf-editor.
You are being too picky :-p
Ok, I fire it as user, then search for "/apps/gnome-power-manager/timeout/sleep_computer_ac". I find it, and it contains:
sleep computer ac: 0 <===== sleep computer battery: 1200 sleep display ac: 300 sleep display battery: 300
This are obviously the settings for the current user, not the defaults for all users.
So, at least as user I can't change it. And I guess that as root it would change the setting for the root desktop, not all users either - if I could run gconf as root, that I can't.
Please carefully read http://lists.opensuse.org/opensuse-factory/2008-10/msg00549.html
Note that you can right-click on a setting and make it the default for all users.
No, you can not. Or maybe you can, but I can't. When I try I get this message box: ] The application "gconf-editor" attempted to change an aspect of ] your configuration that your system administrator or operating ] system vendor does not allow you to change. Some of the settings ] you have selected may not take effect, or may not be restored ] next time you use the application. Clicking Details, I get: No database available to save your configuration: Unable to store a value at key '/apps/gnome-power-manager/timeout/sleep_computer_ac', 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 - -- Cheers / Saludos, Carlos E. R. (from 11.1-factory) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkkEa34ACgkQU92UU+smfQVMYQCfY8O+WwNb01pUF3kjgt9Z22Iy KQoAniKwrmAJM9HgHYGHahb8Xy2qRMcj =Kjix -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org