在为 gnome-terminal 装入或保存配置信息时发生错误。怎么回事呢？

python

不知道什么时候起的，当用Root-Terminal时，就会出现错误提示，内容如下：

在为 gnome-terminal 装入或保存配置信息时发生错误。您的某些配置设置可能不能正常工作。

联系配置服务器失败；某些可能原因是需要为 ORBit 启用 TCP/IP 联网，或者由于系统崩溃，您的 NFS 锁定已失效。请访问 http://www.gnome.org/projects/gconf/ 了解详细信息。(详细信息 -  1: 获取到会话的连接失败：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.)

但用普通用户登入是没有错误的提示。怎么回事呢？

虽然没什么大碍，但觉得不爽呢！

python

难道就是没有人遇到过么？？

jobinson99

和gconf是否独占有关
I'm having a lock file problem. What do I do?
Usually a problem here involves either NFS, or a kernel bug.
The per-user daemon locks two files in the default configuration:
~/.gconfd/lock/ior
~/.gconf/%gconf-xml-backend.lock/ior

The first lock is to ensure that only one gconfd is running. The second lock is to ensure only one program accesses the XML config source at a time.（需要保证独占运行——同时运行两个也是可以的，但会出现另外的问题，看这部分：Can I bypass the lockfile stuff?）

If you have an NFS-mounted home directory, you must be running an rpc.statd/rpc.lockd setup on both NFS client and NFS server, so that file locking works.

If the kernel crashes (or the power cord gets pulled) on an NFS client machine, theoretically when you reboot the client machine it will notify the NFS server that it has rebooted and all previously-held locks should be released.
However, many operating systems including Red Hat Linux 7.2 do not properly do this; so you will have stale locks after a crash.
（理论上重启能解决问题，但很多系统却不能正确做到这个）
If no gconfd is running, these locks may safely be removed. If gconfd is running though, DO NOT remove them; if you have two gconfd processes for a single user, bad things may happen to that user's preferences once in a while.（如果没有gconfd运行，可以删了locks，如果有gconfd运行，千万别删了locks，如果同时一个用户同时有两个gconfd 运行，后果就是楼主的情况，root terminal界面丢失）

在debian下，开启两个需要root用户的进程，必然出现这个问题，比如打开root terminal＋新立得。

python

谢谢你这么详细的解答。今早升级完后发现又正常了。。