CentOS

After wasting countless hours troubleshooting this issue, I'm posting this in case others run into it.

Symptom - User starts a vncserver GUI session with no problems, but when they connect, all that displays is a black screen. The log file in ~/.vnc show these errors:

Xvnc TigerVNC 1.8.0 - built Dec 1 2017 23:21:52
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11903000, The X.Org Foundation


Mon Apr 30 14:48:00 2018
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5912
vncext: created VNC server for screen 0

(imsettings-check:28470): IMSettings-WARNING **: Could not connect: Connection refused

(imsettings-check:28470): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.

** (process:28385): WARNING **: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Connection refused

Solution - The root cause turned out to be a PATH setting in the user's .bashrc file that pointed to an alternate version of dbus-daemon instead of the standard one in /bin. The culprit in my case was an installation of Anaconda Python in the user's home directory. Setting PATH back to the defaults resolved the issue.

Hi, IndyMark

Thanks, you saved my day.
Add a comment before #export PATH="/root/anaconda3/bin:$PATH" then solve the black screen problem.
But is there a way to keep Anaconda3 python in $PATH ?

Well...

a) don't vnc as root in the first place
b) we supply anaconda already, why are you doing source installs?

I'm having the same problem. How do I fix this?

If it is genuinely the same problem then by removing the anaconda3 directory from PATH.

I spent a lot of time in looking for how to fix the same issue; many thanks for your feedback

Paul

This works but my problem now is how to make both TurboVnc and anaconda work together. I really don't want to remove anaconda from the path. Any idea how to do this?

Since this anaconda seems to add to the PATH of the root user, DON'T vnc AS ROOT? That ought to be a good start.

Otherwise, I'd suggest using a script to invoke anaconda that sets the PATH prior to invoking it and revert the PATH in .bash* to not add it at all.