tightvnc error: Could not acquire name on session bus
by taylorkh from LinuxQuestions.org on (#52E2J)
I installed tightvncserver version 1.3.10-0ubuntu5 on Ubuntu Mate 20.04 (beta). This is the FIRST time in 20+ years that I have been able to use a VNC program right from the install without some painful researching and tweaking. Well almost. While I have a vncserver running as :1 I am able to connect remotely to it using vinagre on my CentOS 7 workstation. However, if I attempt to logon to the console of the Ubuntu machine I get an error "Could not acquire name on session bus." Conversely if I am logged onto the console of the Ubuntu machine first I get that same error when trying to connect remotely to my tightvnc server at :1. I tried running the tightvnc server at :2 but that did not help.
With other VNC programs (vncserver, vnc4server, tigervncserver) I have always had to deal with a script ~/.vnc/xstrartup which requires some tweaking. This file contains the lines:
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
I suspect they have something to do with my current issue. However, there is no such script for tightvnc. At least none that I can find. Is there a way to configure tightvnc so that I can connect to the console AND a remote session at the same time? I do not necessarily wish to look at the same desktop. In fact, I would rather the tightvnc establish a separate desktop/session from the console. I can use x11vnc if I wish to SHARE the console desktop.
TIA,
Ken
With other VNC programs (vncserver, vnc4server, tigervncserver) I have always had to deal with a script ~/.vnc/xstrartup which requires some tweaking. This file contains the lines:
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
I suspect they have something to do with my current issue. However, there is no such script for tightvnc. At least none that I can find. Is there a way to configure tightvnc so that I can connect to the console AND a remote session at the same time? I do not necessarily wish to look at the same desktop. In fact, I would rather the tightvnc establish a separate desktop/session from the console. I can use x11vnc if I wish to SHARE the console desktop.
TIA,
Ken