As I stated. I've found Turbo VNC seems to work very well. At my home, I've got a notebook, and use it to vnc into 6 other Fedora 39 machines, and two windows machines in house. Also, vnc into remote machines in mom's house in Nevada. Windows machines all with the tigervnc since Turbo is link only for server. Does have a windows viewer. Right non at Mom's in Nevada from Guam. Brought 2 notebooks, and now local vnc into her machines, and can vnc back to my machines in Guam with no issues. Think Tigervnc was still able to work with up to Fedora 38, but 39 had it stop working even with the xfce. So moved everything to the Turbovnc with linux. Author has responded to quiestions, so seems active. Am also other the Tigervnc list, and TurboVNC also is on it. So, good luck and hope you find a solution that will meet your needs. Note. I did uninstall most of tigervnc packages. Only left these rpm -qa | grep tiger libtiger-0.3.4-26.fc39.x86_64 tigervnc-license-1.13.1-11.fc39.noarch tigervnc-server-minimal-1.13.1-11.fc39.x86_64 Since if try to remove them, it comes up with all kinds of other packages that it wants to remove. Not sure if libtiger is even linked to tigervnc, but it shows up. turbovnc-3.1.1-20240127.x86_64 is the turbovnc package. Installation has $ du /opt/TurboVNC/ | sort -n 4 /opt/TurboVNC/java/jre/legal/java.datatransfer 4 /opt/TurboVNC/java/jre/legal/java.logging 4 /opt/TurboVNC/java/jre/legal/java.naming 4 /opt/TurboVNC/java/jre/legal/java.prefs 4 /opt/TurboVNC/java/jre/legal/java.security.jgss 4 /opt/TurboVNC/java/jre/legal/java.security.sasl 4 /opt/TurboVNC/java/jre/legal/jdk.crypto.ec 8 /opt/TurboVNC/java/jre/conf/sdp 12 /opt/TurboVNC/java/jre/conf/security/policy/unlimited 12 /opt/TurboVNC/java/jre/legal/jdk.crypto.cryptoki 16 /opt/TurboVNC/java/jre/conf/security/policy/limited 36 /opt/TurboVNC/java/jre/bin 36 /opt/TurboVNC/java/jre/conf/security/policy 44 /opt/TurboVNC/java/jre/legal/java.desktop 52 /opt/TurboVNC/java/jre/legal/java.xml 96 /opt/TurboVNC/java/jre/legal/java.base 100 /opt/TurboVNC/java/jre/conf/security 104 /opt/TurboVNC/man/man1 108 /opt/TurboVNC/man 128 /opt/TurboVNC/java/jre/conf 236 /opt/TurboVNC/java/jre/legal 416 /opt/TurboVNC/java/jre/lib/security 5980 /opt/TurboVNC/bin 23448 /opt/TurboVNC/java/jre/lib/server 60948 /opt/TurboVNC/java/jre/lib 61356 /opt/TurboVNC/java/jre 63028 /opt/TurboVNC/java 69124 /opt/TurboVNC/ So, works well for me. On 24 Feb 2024 at 15:10, Sam Varshavchik wrote: From: Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: tigervnc server configuration limitation Date sent: Sat, 24 Feb 2024 15:10:33 -0500 Send reply to: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > Francis.Montagnac@xxxxxxxx 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. > > +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@xxxxxxxx mailto:msetzerii@xxxxxxxxx mailto:msetzerii@xxxxxxx Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+ -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
