VNC error: “Could not connect to session bus: Failed to connect to socket”

up vote
1
down vote

favorite

I started a vncserver on display :1 on an ubuntu machine. When I connect to it, I get a grey X window with an error message Could not connect to session bus: Failed to connect to socket.

The vnc log is:

Xvnc Free Edition 4.1.1 - built Apr  9 2010 15:59:33

Copyright (C) 2002-2005 RealVNC Ltd.

See http://www.realvnc.com for information on VNC.

Underlying X server release 40300000, The XFree86 Project, Inc 





Sun Mar 20 15:33:59 2011

 vncext:      VNC extension running!

 vncext:      Listening for VNC connections on port 5901

 vncext:      created VNC server for screen 0

error opening security policy file /etc/X11/xserver/SecurityPolicy

Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list!

cat: /var/run/gdm/auth-for-link2-eGnVvf/database: No such file or directory

gnome-session[24880]: WARNING: Could not make bus activated clients aware of DISPLAY=:1.0 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/dell:@/tmp/.ICE-unix/24880,unix/dell:/tmp/.ICE-unix/24880 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused



Sun Mar 20 15:34:10 2011

 Connections: accepted: 0.0.0.0::51620

 SConnection: Client needs protocol version 3.8 

 SConnection: Client requests security type VncAuth(2)

 VNCSConnST:  Server default pixel format depth 16 (16bpp) little-endian rgb565

 VNCSConnST:  Client pixel format depth 16 (16bpp) little-endian rgb565

gnome-session[24880]: Gtk-CRITICAL: gtk_main_quit: assertion `main_loops != NULL' failed

gnome-session[24880]: CRITICAL: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

Any ideas how to fix it?

edited Mar 20 '11 at 14:58

asked Mar 20 '11 at 13:39

GJ.

3,881165698

I wonder if it's because of this part: error opening security policy file /etc/X11/xserver/SecurityPolicy ...some permissions issue, it needs to access that directory but it isn't allowed? Otherwise, every vnc problem I ever had is because A: I forgot to forward the port or enable DMZ on the router B: I forgot to set both the server and viewer to the specified port (5901 in your case) ...C: I got the wrong IP info (for example if you're connected to a wireless network, and the VNC server is running on the same network, you use the network IP address, not external.
– CreeDorofl
Mar 20 '11 at 15:41

DBus is messed up here. Reinstall it, and try again.
– new123456
Mar 22 '11 at 22:12

add a comment |

up vote
1
down vote

favorite

I started a vncserver on display :1 on an ubuntu machine. When I connect to it, I get a grey X window with an error message Could not connect to session bus: Failed to connect to socket.

The vnc log is:

Xvnc Free Edition 4.1.1 - built Apr  9 2010 15:59:33

Copyright (C) 2002-2005 RealVNC Ltd.

See http://www.realvnc.com for information on VNC.

Underlying X server release 40300000, The XFree86 Project, Inc 





Sun Mar 20 15:33:59 2011

 vncext:      VNC extension running!

 vncext:      Listening for VNC connections on port 5901

 vncext:      created VNC server for screen 0

error opening security policy file /etc/X11/xserver/SecurityPolicy

Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list!

cat: /var/run/gdm/auth-for-link2-eGnVvf/database: No such file or directory

gnome-session[24880]: WARNING: Could not make bus activated clients aware of DISPLAY=:1.0 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/dell:@/tmp/.ICE-unix/24880,unix/dell:/tmp/.ICE-unix/24880 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused



Sun Mar 20 15:34:10 2011

 Connections: accepted: 0.0.0.0::51620

 SConnection: Client needs protocol version 3.8 

 SConnection: Client requests security type VncAuth(2)

 VNCSConnST:  Server default pixel format depth 16 (16bpp) little-endian rgb565

 VNCSConnST:  Client pixel format depth 16 (16bpp) little-endian rgb565

gnome-session[24880]: Gtk-CRITICAL: gtk_main_quit: assertion `main_loops != NULL' failed

gnome-session[24880]: CRITICAL: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

Any ideas how to fix it?

edited Mar 20 '11 at 14:58

asked Mar 20 '11 at 13:39

GJ.

3,881165698

I wonder if it's because of this part: error opening security policy file /etc/X11/xserver/SecurityPolicy ...some permissions issue, it needs to access that directory but it isn't allowed? Otherwise, every vnc problem I ever had is because A: I forgot to forward the port or enable DMZ on the router B: I forgot to set both the server and viewer to the specified port (5901 in your case) ...C: I got the wrong IP info (for example if you're connected to a wireless network, and the VNC server is running on the same network, you use the network IP address, not external.
– CreeDorofl
Mar 20 '11 at 15:41

DBus is messed up here. Reinstall it, and try again.
– new123456
Mar 22 '11 at 22:12

add a comment |

up vote
1
down vote

favorite

I started a vncserver on display :1 on an ubuntu machine. When I connect to it, I get a grey X window with an error message Could not connect to session bus: Failed to connect to socket.

The vnc log is:

Xvnc Free Edition 4.1.1 - built Apr  9 2010 15:59:33

Copyright (C) 2002-2005 RealVNC Ltd.

See http://www.realvnc.com for information on VNC.

Underlying X server release 40300000, The XFree86 Project, Inc 





Sun Mar 20 15:33:59 2011

 vncext:      VNC extension running!

 vncext:      Listening for VNC connections on port 5901

 vncext:      created VNC server for screen 0

error opening security policy file /etc/X11/xserver/SecurityPolicy

Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list!

cat: /var/run/gdm/auth-for-link2-eGnVvf/database: No such file or directory

gnome-session[24880]: WARNING: Could not make bus activated clients aware of DISPLAY=:1.0 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/dell:@/tmp/.ICE-unix/24880,unix/dell:/tmp/.ICE-unix/24880 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused



Sun Mar 20 15:34:10 2011

 Connections: accepted: 0.0.0.0::51620

 SConnection: Client needs protocol version 3.8 

 SConnection: Client requests security type VncAuth(2)

 VNCSConnST:  Server default pixel format depth 16 (16bpp) little-endian rgb565

 VNCSConnST:  Client pixel format depth 16 (16bpp) little-endian rgb565

gnome-session[24880]: Gtk-CRITICAL: gtk_main_quit: assertion `main_loops != NULL' failed

gnome-session[24880]: CRITICAL: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

Any ideas how to fix it?

edited Mar 20 '11 at 14:58

asked Mar 20 '11 at 13:39

GJ.

3,881165698

I started a vncserver on display :1 on an ubuntu machine. When I connect to it, I get a grey X window with an error message Could not connect to session bus: Failed to connect to socket.

The vnc log is:

Xvnc Free Edition 4.1.1 - built Apr  9 2010 15:59:33

Copyright (C) 2002-2005 RealVNC Ltd.

See http://www.realvnc.com for information on VNC.

Underlying X server release 40300000, The XFree86 Project, Inc 





Sun Mar 20 15:33:59 2011

 vncext:      VNC extension running!

 vncext:      Listening for VNC connections on port 5901

 vncext:      created VNC server for screen 0

error opening security policy file /etc/X11/xserver/SecurityPolicy

Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list!

Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list!

cat: /var/run/gdm/auth-for-link2-eGnVvf/database: No such file or directory

gnome-session[24880]: WARNING: Could not make bus activated clients aware of DISPLAY=:1.0 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused 

gnome-session[24880]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/dell:@/tmp/.ICE-unix/24880,unix/dell:/tmp/.ICE-unix/24880 environment variable: Failed to connect to socket /tmp/dbus-FhdHHIq8jt: Connection refused



Sun Mar 20 15:34:10 2011

 Connections: accepted: 0.0.0.0::51620

 SConnection: Client needs protocol version 3.8 

 SConnection: Client requests security type VncAuth(2)

 VNCSConnST:  Server default pixel format depth 16 (16bpp) little-endian rgb565

 VNCSConnST:  Client pixel format depth 16 (16bpp) little-endian rgb565

gnome-session[24880]: Gtk-CRITICAL: gtk_main_quit: assertion `main_loops != NULL' failed

gnome-session[24880]: CRITICAL: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

Any ideas how to fix it?

linux vnc vncserver

edited Mar 20 '11 at 14:58

asked Mar 20 '11 at 13:39

GJ.

3,881165698

edited Mar 20 '11 at 14:58

asked Mar 20 '11 at 13:39

GJ.

3,881165698

edited Mar 20 '11 at 14:58

asked Mar 20 '11 at 13:39

GJ.

3,881165698

asked Mar 20 '11 at 13:39

GJ.

3,881165698

asked Mar 20 '11 at 13:39

GJ.

3,881165698

I wonder if it's because of this part: error opening security policy file /etc/X11/xserver/SecurityPolicy ...some permissions issue, it needs to access that directory but it isn't allowed? Otherwise, every vnc problem I ever had is because A: I forgot to forward the port or enable DMZ on the router B: I forgot to set both the server and viewer to the specified port (5901 in your case) ...C: I got the wrong IP info (for example if you're connected to a wireless network, and the VNC server is running on the same network, you use the network IP address, not external.
– CreeDorofl
Mar 20 '11 at 15:41

DBus is messed up here. Reinstall it, and try again.
– new123456
Mar 22 '11 at 22:12

add a comment |

I wonder if it's because of this part: error opening security policy file /etc/X11/xserver/SecurityPolicy ...some permissions issue, it needs to access that directory but it isn't allowed? Otherwise, every vnc problem I ever had is because A: I forgot to forward the port or enable DMZ on the router B: I forgot to set both the server and viewer to the specified port (5901 in your case) ...C: I got the wrong IP info (for example if you're connected to a wireless network, and the VNC server is running on the same network, you use the network IP address, not external.
– CreeDorofl
Mar 20 '11 at 15:41

DBus is messed up here. Reinstall it, and try again.
– new123456
Mar 22 '11 at 22:12

I wonder if it's because of this part: error opening security policy file /etc/X11/xserver/SecurityPolicy ...some permissions issue, it needs to access that directory but it isn't allowed? Otherwise, every vnc problem I ever had is because A: I forgot to forward the port or enable DMZ on the router B: I forgot to set both the server and viewer to the specified port (5901 in your case) ...C: I got the wrong IP info (for example if you're connected to a wireless network, and the VNC server is running on the same network, you use the network IP address, not external.
– CreeDorofl
Mar 20 '11 at 15:41

DBus is messed up here. Reinstall it, and try again.
– new123456
Mar 22 '11 at 22:12

add a comment |

1 Answer
1

active

oldest

votes

up vote
1
down vote

try restarting messagebus service.

service messagebus restart

answered Sep 19 '17 at 5:37

user219318

391

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f259943%2fvnc-error-could-not-connect-to-session-bus-failed-to-connect-to-socket%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
1
down vote

try restarting messagebus service.

service messagebus restart

answered Sep 19 '17 at 5:37

user219318

391

add a comment |

up vote
1
down vote

try restarting messagebus service.

service messagebus restart

answered Sep 19 '17 at 5:37

user219318

391

add a comment |

up vote
1
down vote

try restarting messagebus service.

service messagebus restart

answered Sep 19 '17 at 5:37

user219318

391

try restarting messagebus service.

service messagebus restart

answered Sep 19 '17 at 5:37

user219318

391

answered Sep 19 '17 at 5:37

user219318

391

answered Sep 19 '17 at 5:37

user219318

391

answered Sep 19 '17 at 5:37

user219318

391

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Gfrktyl