can use gui on {console, ssh -X} using my account and vnc using new accounts but not using vnc with my account. Help

[chankim]

In my CentOS 6.9 machine, I can use gui tools (my user id is ckim)
1. on console using ckim
2. using ssh -X ckim@'ip addr'
3. using vnc with a new account test1
but I cannot use vnc with my account!

I found after logging into my account using 'ssh -X', I have .Xauthority file in my home.
But when I connect to my vnc window, I have this 'Failed to connect to socket /tmp/dbus-.... : connection refused' message.

If I see /var/log/message file, I can see

May 2 21:53:42 stph45 ck-xinit-session: error connecting to console-kit
May 2 21:53:42 stph45 gnome-session[10407]: WARNING: Could not make bus activated clients aware of DISPLAY=:1 environment variable: Failed to connect to socket /tmp/dbus-iFMomXG0Fu: ~W�결~]� 거�
~@~P�
May 2 21:53:42 stph45 gnome-session[10407]: 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-iFMomXG0Fu: ~W�결~]� 거~@~P�
May 2 21:53:42 stph45 gnome-session[10407]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/10407,unix/unix:/tmp/.ICE-unix/10407 environment variable: Failed to connect to socket /tmp/dbus-iFMomXG0Fu: ~W�결~]� 거~@~P�

What should I do?
ADD : I found with vnc connection (with my account), it's all black screen with just the mouse. (no dbus socket connecting message). and my 'xauth list' command shows
key values for myhost{/unix:10, :1, /unix:1, :2, /unix2} connections. My old backup .Xauthority file showed more key values and it contains 'localhost:1' entry. Is this the entry for vnc connection?

[chankim]

wow, there's no comment yet.
Here is my .vnc/mymachine:1.log file.

Xvnc TigerVNC 1.1.0 - built Mar 22 2017 18:06:28
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11704000, The X.Org Foundation


Fri May 4 20:13:39 2018
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: created VNC server for screen 0
MainThread 2018/05/04 20:13:42.9844 (sabayon-apply): Applying profile '/etc/sabayon/profiles/xguest.zip' for user 'ckim'
MainThread 2018/05/04 20:13:43.1253 (sabayon-apply): Finished applying profile '/etc/sabayon/profiles/xguest.zip' for user 'ckim'
===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) =====
MainThread 2018/05/04 20:13:42.9844 (sabayon-apply): Applying profile '/etc/sabayon/profiles/xguest.zip' for user 'ckim'
MainThread 2018/05/04 20:13:43.1253 (sabayon-apply): Finished applying profile '/etc/sabayon/profiles/xguest.zip' for user 'ckim'
===== END MILESTONES (/usr/sbin/sabayon-apply) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) =====
MainThread 2018/05/04 20:13:42.9844 (sabayon-apply): Applying profile '/etc/sabayon/profiles/xguest.zip' for user 'ckim'
MainThread 2018/05/04 20:13:43.1253 (sabayon-apply): Finished applying profile '/etc/sabayon/profiles/xguest.zip' for user 'ckim'
===== END RING BUFFER (/usr/sbin/sabayon-apply) =====


This configuration for the debug log can be re-created
by putting the following in ~//etc/sabayon/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000

(process:4234): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported
gnome-session[4156]: WARNING: Could not make bus activated clients aware of DISPLAY=:1 environment variable: Failed to connect to socket /tmp/dbus-AlvHtsJCMO: ~W�결~]� 거~@~P�
gnome-session[4156]: 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-AlvHtsJCMO: ~W�결~]� 거~@~P�
gnome-session[4156]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/4156,unix/unix:/tmp/.ICE-unix/4156 environment variable: Failed to connect to socket /tmp/dbus-AlvHtsJCMO: ~W�결~]� 거~@~P�

Fri May 4 20:13:52 2018
Connections: accepted: 129.254.132.39::59027
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)

Fri May 4 20:13:56 2018
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888
gnome-session[4156]: Gtk-CRITICAL: IA__gtk_main_quit: assertion `main_loops != NULL' failed
gnome-session[4156]: CRITICAL: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
gnome-session[4156]: Gtk-CRITICAL: IA__gtk_main_quit: assertion `main_loops != NULL' failed
gnome-session[4156]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
gnome-session[4156]: CRITICAL: error getting session bus: Failed to connect to socket /tmp/dbus-AlvHtsJCMO: ~W�결~]� 거~~
@~P�
gnome-session[4156]: WARNING: Unable to register presence with session bus
gnome-session[4156]: CRITICAL: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
GConf ~X�~X: ~D�| ~U ~D~\~D~W~P ~W�결~U~X~J~T~M� ~K�~L�~V~H~J�~K~H~K�. ~[~P~]�~]~@ ORBit~W~P TCP/IP ~~
D�~J�~[~L~A�를 ~B�~Z�~U~X~J~T 경~Z�~]�거~B~X, ~U~D~K~H면 ~K~\~J�~E~\~]~X ~]�~C~A ~E~L~\ ~]�~U� NN
FS ~^| ~H~]� ~O~Y~^~Q~U~X~@ ~U~J~L ~P~X~W~H~]~D 경~Z�~^~E~K~H~K�. ~^~P~D�~U~\ | ~U보~J~T <http://proo
jects.gnome.org/gconf/> ~N~X~]�~@를 참조~U~X~K�~K~\~X�. (~^~P~D�~U~\ | ~U보 - 1: ~D�~E~X~W~P ~W�결~U~X�
~J~T~M� ~K�~L�~V~H~J�~K~H~K�: Failed to connect to socket /tmp/dbus-AlvHtsJCMO: ~W�결~]� 거~@~P�)
GConf ~X�~X: ~D�| ~U ~D~\~D~W~P ~W�결~U~X~J~T~M� ~K�~L�~V~H~J�~K~H~K�. ~[~P~]�~]~@ ORBit~W~P TCP/IP ~~
D�~J�~[~L~A�를 ~B�~Z�~U~X~J~T 경~Z�~]�거~B~X, ~U~D~K~H면 ~K~\~J�~E~\~]~X ~]�~C~A ~E~L~\ ~]�~U� NN
FS ~^| ~H~]� ~O~Y~^~Q~U~X~@ ~U~J~L ~P~X~W~H~]~D 경~Z�~^~E~K~H~K�. ~^~P~D�~U~\ | ~U보~J~T <http://proo
jects.gnome.org/gconf/> ~N~X~]�~@를 참조~U~X~K�~K~\~X�. (~^~P~D�~U~\ | ~U보 - 1: ~D�~E~X~W~P ~W�결~U~X�
~J~T~M� ~K�~L�~V~H~J�~K~H~K�: Failed to connect to socket /tmp/dbus-AlvHtsJCMO: ~W�결~]� 거~@~P�)

@

[chankim]

Hope someone who knows what is going on see this.
After trying many things to solve this problem from time to time while I do my main job,
and remembering that a new account can use vnc, I decided to make a new account with the same user name/ID and group name/ID with my current account. my original account was ckim, user ID 1000, in group ckim and group ID 1000.
So I moved /home/ckim to /home/ckim.org and removed account ckim.
THen, I created new account ckim, with same user ID, group and group ID.
I checked I can use vnc again with the new account.
Rather than moving all the files and directories from /home/ckim.org to /home/ckim,
I tried to fool the OS and made /home/ckim.org back to /home/ckim and make /home/ckim to /home/ckim.new.
Then the 'cannot connect to the socekt.. dbus..' appeared again!
If I switch my home directory to the newly created home directory, I can use vnc again.
Of course I can copy or move files/directories from my old account home to a new home, but
this phenomenon suggests that the problem is in my home directory, not in the system directories.

Here is the files starting with . (dot) under my old home directory.
Because I started OS upgrade from March 14 (from centos 6.7 to centos 6.9), I showed files newer than that date.
I guess if I remove a file or directory from the old home directory, I could just switch to my old home directory.
The suspect seems to be one of .gnome2, .gconfd, .gonf.*, .xsession-errors.old, .dbus, .xsession-errors, .Xauthority.
What file/directory could be causing this vnc connection problem? (please see my previous comment about vnc log)

drwxr-xr-x 11 ckim ckim 4096 2018-02-21 23:08 .gnome2/
-rw------- 1 ckim ckim 88 2018-03-19 09:35 .python_history
drwxr----- 2 ckim ckim 4096 2018-03-19 10:32 .ssh/
-rw------- 1 ckim ckim 59 2018-03-20 10:38 .lesshst
-rw-rw-r-- 1 ckim ckim 149 2018-04-02 22:03 .vimsize
drwxr-xr-x 2 ckim ckim 4096 2018-04-03 09:37 .fontconfig/
-rw-rw-r-- 1 ckim ckim 1058 2018-04-03 11:16 .bzr.log
drwx------ 2 ckim ckim 4096 2018-04-04 20:35 .gconfd/
-rw-rw-r-- 1 ckim ckim 2818 2018-04-11 10:55 .vimrc
drwx------ 2 ckim ckim 4096 2018-04-23 09:57 .gconf.xml.mandatory/
drwx------ 2 ckim ckim 4096 2018-04-23 09:57 .gconf.xml.defaults/
-rw------- 1 ckim ckim 359935 2018-04-23 15:48 .xsession-errors.old
drwxr-xr-x 4 ckim ckim 4096 2018-04-30 15:15 .vim/
-rw-r--r-- 1 ckim ckim 58370 2018-05-02 17:57 .cshrc
drwxrwxr-x 2 ckim ckim 4096 2018-05-02 21:40 .simvision/
drwx------ 4 ckim ckim 4096 2018-05-03 21:26 .ddd/
drwx------ 3 ckim ckim 4096 2018-05-04 20:24 .dbus/
drwxr----- 2 ckim ckim 4096 2018-05-04 20:24 .gnupg/
-rw-rw-r-- 1 ckim ckim 132 2018-05-04 20:24 .gtk-bookmarks
-rw-rw-r-- 1 ckim ckim 11212 2018-05-04 21:02 .viminfo
-rw------- 1 ckim ckim 82123 2018-05-04 21:04 .xsession-errors
-rw-rw-r-- 1 ckim ckim 432 2018-05-04 22:21 .imsettings.log
-rw-rw-r-- 1 ckim ckim 45 2018-05-04 22:21 .gconf.path.mandatory
-rw-rw-r-- 1 ckim ckim 44 2018-05-04 22:21 .gconf.path.defaults
-rw-r-----. 1 ckim ckim 113120 2018-05-04 22:21 .ICEauthority
drwxr----- 4 ckim ckim 4096 2018-05-04 22:21 .gconf/
-rw------- 1 ckim ckim 600 2018-05-04 22:26 .Xauthority
drwxrwxr-x 2 ckim ckim 4096 2018-05-04 22:26 .vnc/
-rw------- 1 ckim ckim 9046 2018-05-04 22:26 .history
drwxr-xr-x 7 root root 4096 2018-05-04 22:26 ../
drwxr-x--- 241 ckim ckim 20480 2018-05-04 23:25 ./

[chankim]

I just moved .cshrc, .gconf and .mozilla folders from my old home directory to my new home directory.
and now can use my ordinary stuff. all the web related setting are recovered including centos.org password,
and my terminal settings are as before. I have a complete backup of previous home directory so I can move stuff
one by one when I meet any inconveniences.
This is not the way I want my problem solved, but it's another easy approach in case anyone experiences this kind of problem.
Hope somebody get help from this.