Couldn‘t connect to session bus: Did not receive a reply. Possible causes include: the remote applic
Posted Dontla
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Couldn‘t connect to session bus: Did not receive a reply. Possible causes include: the remote applic相关的知识,希望对你有一定的参考价值。
运行进程间通信dbus服务程序和客户程序时报错:
Couldn't connect to session bus: 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.
原因:
不能在root用户下运行,(可能这创建的是session dbus的原因,而不是system dbus),用exit退出root用户到普通用户下运行就好了
参考文章:Couldn’t connect to session bus问题的解决
以上是关于Couldn‘t connect to session bus: Did not receive a reply. Possible causes include: the remote applic的主要内容,如果未能解决你的问题,请参考以下文章
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?
《转》couldn't connect to server 127.0.0.1:27017 at src/mongo/shell/mongo.js:145
Couldn‘t connect to session bus: Did not receive a reply. Possible causes include: the remote applic
使用webstorm连接github提示:Error connecting to Gitosc: Couldn't parse Gitee response的解决方法
解决couldn't connect to server 172.21.4.208:27 017 at src/mongo/shell/mongo.js:147