Francis.Montagnac(a)inria.fr writes:
Hi.
On Sat, 24 Feb 2024 11:52:40 -0500 Sam Varshavchik wrote:
> But something is still broken. I went through the motions, set
session=xfce,
> ... and that was because even xfce is not going to work. The reason was
> dumped into ~/.vnc/*log:
> /usr/bin/startxfce4: X server already running on display :1
> MESA: error: ZINK: failed to choose pdev
> glx: failed to create drisw screen
> failed to load driver: zink
> xfce4-session-Message: 11:40:42.960: SSH authentication agent is already
running
> xinit: connection to X server lost
It works by setting in ~/.vnc/config:
session=xfce4
not session=xfce.
Seems that /usr/sbin/vncsession calls then xfce4-session.
I don't have an xfce-session command on my machine.
This is at odds with the HOWTO in the tigervnc-server package, which states:
=====================================================
### Note:
There is one important option you need to set and that option is the session you
want to start. E.g when you want to start GNOME desktop, then you have to use
“`
session=gnome
“`
which should match the name of a session desktop file from
`/usr/share/xsessions` directory.
=====================================================
And here's what I have:
# ls /usr/share/xsessions
gnome.desktop gnome-xorg.desktop xfce.desktop
That's where "session=xfce" came from. So I changed it to xfce4. This time
it started. No wanting to believe my luck I connected with vncviewer...
... and I ended up looking at Gnome's login screen. The invalid
"session=xfce4" setting was ignored, and the session defaulted to Gnome.
So, it's true that one can be logged into an XFCE desktop and be able to
start a Gnome VNC session. But that does me no good.