On 24 Feb 2024 at 10:10, Sam Varshavchik wrote: From: Sam Varshavchik <mrsam(a)courier-mta.com&gt; To: Fedora Users List <users(a)lists.fedoraproject.org&gt; Subject: tigervnc server configuration limitation Date sent: Sat, 24 Feb 2024 10:10:42 -0500 Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org&gt; Not sure on the latest version of tigervnc on Fedora, for a while I was able to have it work, but had to change the configuration to have the vnc use XFCE (heard others had used mate or other) but the wayland/gnome 3 definitely do not allow for dual user sessions local/vnc. I eventually moved to using turbovnc. https://turbovnc.org/ It installs in /opt/TurboVNC/ with the programs in bin subdirectory. Configuration is done via /etc/sysconfig/tvncserver Note change port number to xx and changed user id to userid. Would need to select your userid and the port want to use. 5900+xx One thing. I create a link to the vncviewer since it doesn't place file in /usr/bin /usr/bin/vncviewer -> /opt/TurboVNC/bin/vncviewer I do have it set to use -wm xfce, so would need to install the xfce group, or whatever desktop manager you want. If nothing else an option that might work for you. # The VNCSERVERS variable is a list of display:user pairs, separated by # spaces. # # Uncomment the first line below to start a TurboVNC session under the account # 'myusername' (adjust this to your own username) and listening on Display :1. # You will also need to configure a VNC password (run # 'man -M {TurboVNC_directory}/man vncpasswd' for instructions) or another form # of authentication. See the TurboVNC User's Guide for more information about # the authentication methods available in TurboVNC. If you intend to connect # to the TurboVNC session over an untrusted network, then it is strongly # recommended that you configure the session to require TLS or SSH encryption. # Refer to the TurboVNC User's Guide and the Xvnc man page # ('man -M {TurboVNC_directory}/man Xvnc') for more information. Set the # VNCSERVERARGS[n] variable in order to specify arguments that should be passed # to vncserver when creating the TurboVNC session for Display :n. Refer to # the TurboVNC Server man pages ('man -M {TurboVNC_directory}/man vncserver' # and 'man -M {TurboVNC_directory}/man Xvnc') for a list of possible arguments. # VNCSERVERS="1:myusername" # VNCSERVERARGS[1]="" VNCSERVERS="xx:userid" VNCSERVERARGS[xx]="-wm xfce -geometry 1600x845" It does create a systemd thing?? systemctl status tvncserver ● tvncserver.service - LSB: Starts and stops the TurboVNC Server Loaded: loaded (/etc/rc.d/init.d/tvncserver; generated) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (exited) since Thu 2024-02-22 15:51:40 ChST; 2 days ago Docs: man:systemd-sysv-generator(8) CPU: 36ms +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com mailto:msetzerii@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+

Sam Varshavchik writes: ... 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 So this is not a Gnome limitation, but a systemd limitation.

Francis.Montagnac(a)inria.fr writes: 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.

Michael D. Setzer II via users writes: I hear you. I'm not married to tigervnc, just not sure if trying to get turbovnc installed and set up will be more or less work, given that, it appears, it's not in Fedora, but in an external repository, with everything that that means. The issue is not with tigervnc itself, but with its packaging. My recollection of the early days of Fedora is that the guiding principle was to stay close to upstream packaging. This is not happening anymore.

On 2/24/24 08:52, Sam Varshavchik wrote: It's an X limitation or an operating system limitation if you really want to call it that. There can only be one X server on a port. Change the display number. I run a VNC server with openbox using systemd and it works fine.

On 2/24/24 08:52, Sam Varshavchik wrote: You say the reason is there, but what reason are you seeing? The only difference from when it does work is that last line from xinit. (I was mistaken about the "already running" message. That should happen because Xvnc is started and xfce should not be starting an X server.) It does have something to do with running from systemd, but I have no idea what it is. The xfce session starts, but something fails. If you run the same command directly, it starts up correctly.

On 2/24/24 23:17, Francis.Montagnac(a)inria.fr wrote: It's directly related to running from systemd while the user is already logged in. If the user isn't logged in, it works fine from systemd. If the user is logged in and you start it from the command line, it also works. So it's only the combination. I did run a strace, but it's not clear what's going on. It almost seems like it's something to do with the ssh agent, but I wasn't motivated enough to really follow it.

On Sun, 25 Feb 2024 09:11:34 +0100 Francis.Montagnac(a)inria.fr wrote: I tried to no avail 1) to call xfce4-session through ssh-agent 2) to unset SSH_AUTH_SOCK SSH_AGENT_PID before calling xfce4-session 3) to chown root /tmp/.ICE-unix/ I give up trying to allow an xfce session at the console and under VNC. This is not possible also with MATE: the VNC session, started after the one at the console, is blocked on: Could not acquire name on session bus Close and then nothing is usable. As samuel said earlier, having two sessions may: cause great confusion and weird happenings. I have a workaround. For years, I use only a VNC session. When at the console I only connect to it with a vncviewer "session" defined as: [Desktop Entry] Version=1.0 Name=vncviewer1 Session Exec=vncviewer :1 Icon= Type=Application DesktopNames=VNCVIEWER1 otherwise, I connect to it with "vncviewer -via". I don't need to have GPU acceleration. This may be available with vglrun, when at the console. -- francis

On 2/25/24 06:35, Jonathan Billings wrote: It's a valid option, but I don't see how it's relevant to this issue. There's no port conflict.

Samuel Sieb writes: I don't know what to tell you except that it works. I just VNCed into the Ubuntu box, and 'ps -ef' tells me I have two sessions running: mrsam 1883 1846 0 10:00 ? 00:00:00 xfce4-session mrsam 5411 5408 0 16:37 ? 00:00:00 xfce4-session And just to make sure I wasn't nuts: I went over to the Ubuntu box and turned on the monitor: yup, I'm logged in, on an XFCE desktop. And I just disconnected a VNC session to the remote XFCE desktop. They are different desktops: $ tr '\0' '\012' </proc/1883/environ | grep DISPLAY DISPLAY=:0 $ tr '\0' '\012' </proc/5411/environ | grep DISPLAY DISPLAY=:1 No problems doing this on Ubuntu.

x11vnc works at least with x11 (not sure about wayland) and can be run on a running session to create a vnc connection to that live session. I used it to remotely view/control my active laptop screen. On Sat, Feb 24, 2024 at 9:11 AM Sam Varshavchik <mrsam(a)courier-mta.com&gt; wrote: > > I'm not sure when Fedora switched to the current tigervnc systemd-based > configuration, but: > > I've been using tigervnc to log in to an Ubuntu box, and it was simple to > set up tigervnc on Ubuntu for remote access. I just tried the same on Fedora > and was informed that launching vncserver was "deprecated", and pointed > towards the documentation for Fefora's systemd-based configuration. > > Reading through that, the following limitation is a showstopper for me: > > # # Limitations > # You will not be able to start a Tigervnc server for a user who is already > # logged into a graphical session. > > That's a no-go for me. My Fedora system is configured to automatically log > into a graphical desktop. This won't work for me, then. > > This is not a limitation on Ubuntu. It's too bad that Fedora cannot do the > same. > > -- > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue