Configuration server couldn't be contacted: D-BUS

Posted 2021-02-28 paulligo

在使用starDict时，会出现以下报错：

Configuration server couldn‘t be contacted: D-BUS error: Unable to store a value at key ‘/apps/stardict/manage_dictionaries/dict_default_group‘, 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

经查证与家目录下面的.dbus权限有关

ls -al ~ |grep .dbus

sudo chown -R $user:$user ~/.dbus

若linux图形界面出现这个问题均可以尝试此方式处理