Forum Replies Created
-
Posts
-
Thank you. Before I go can I ask you one thing please.
I removed xfce and installed MATE desktop, which works now.
[root@db ~]# grep Exec /usr/share/xsessions/*
/usr/share/xsessions/gnome-classic.desktop:Exec=env GNOME_SHELL_SESSION_MODE=classic gnome-session –session gnome-classic
/usr/share/xsessions/gnome-classic.desktop:TryExec=gnome-session
/usr/share/xsessions/gnome.desktop:Exec=gnome-session
/usr/share/xsessions/gnome.desktop:TryExec=gnome-session
/usr/share/xsessions/mate.desktop:Exec=mate-session
/usr/share/xsessions/mate.desktop:TryExec=mate-session
I have my node.cfg as below:
#DefaultDesktopCommand “/etc/X11/xinit/Xsession default”
#DefaultDesktopCommand “/usr/bin/openbox”
#DefaultDesktopCommand “/usr/bin/openbox-session”
DefaultDesktopCommand “/usr/bin/gnome-session”
Now when I connect to the ETS via nomachine, it takes me straight to the linux desktop rather than the nomachine connections page where I can create a new virtual desktop connection. Do I need to change the DefaultDesktopCommand setting or anything in the ETS server.config?
Thanks
ETS runs on CentOS 7. I manually installed MATE GUI but had to uninstall as it didn’t work. I then manually installed xfce GUI.
However CentOS machine doesn’t invoke GUI when restarted. Just wondering if this imperfect GUI environment has anything to do with setting up virtual desktop connection.
My node.cfg(the top two commands didn’t work)
#DefaultDesktopCommand “/etc/X11/xinit/Xsession default”
#DefaultDesktopCommand “/usr/bin/openbox”
#DefaultDesktopCommand “/usr/bin/openbox-session”
DefaultDesktopCommand “/etc/X11/xinit/Xsession openbox-session”