debian(wheezy) gvim GConf-WARNING **: Client failed to connect to the D-BUS daemon:
oot@debian:/# gvim 1.txt
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
(gvim:6040): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
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.
D-bus 수호 프로세스가 열리지 않았다는 뜻입니다. 관건은 루트로 활성화된 것입니다.예전에는 나타나지 않았어요.요즘 너무 빨리 자르는 것 같아서 Alias의 sr=su root를 썼는데 su를 안 썼어요.
루트 로그인 환경이 없습니다.즉, 로딩이 적게 됩니다~/.bash_프로필, 상응하는 권한 부여 지원이 부족합니다.
그래서 간단합니다. 알리스의 sr=su root를 su-또는su-root로 바꾸면 됩니다.
또는/usr/bin/gvim를 dbus-launch--exit-with-session/usr/bin/gvim로 바꿔서 gvim를 시작합니다. 그러나 이것은session을 받지 못해서 오류가 발생합니다.
(gvim:6642): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
gnu, bsd 명령의 차이를 흡수linux와 기타 unix, 예를 들어 맥 등 쌍방을 사용합니다 환경적인 사람도 많죠. 이런 상황에서gnu명령일까,bsd명령일까,항상 혼란스러워요. 또한 리눅스에서 데비안 계열은 가wk가 아니라 마wk의 적은 기능이...
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.