On 24 Feb 2024 at 16:55, 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 16:55:05 -0500
Send reply to: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>
> Michael D. Setzer II via users writes:
>
> > 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.
>
> 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.
>
>
The repo file is:
cat TurboVNC.repo
[TurboVNC]
name=TurboVNC official RPMs
baseurl=https://packagecloud.io/dcommander/turbovnc/rpm_any/rpm_any/$basearch
repo_gpgcheck=1
gpgcheck=1
gpgkey=https://packagecloud.io/dcommander/turbovnc/gpgkey
https://raw.githubusercontent.com/TurboVNC/repo/main/VGL-GPG-KEY
https://raw.githubusercontent.com/TurboVNC/repo/main/VGL-GPG-KEY-1024
enabled=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
metadata_expire=6h
skip_if_unavailable=True
[TurboVNC-source]
name=TurboVNC official SRPMs
baseurl=https://packagecloud.io/dcommander/turbovnc/rpm_any/rpm_any/SRPMS
repo_gpgcheck=1
gpgcheck=1
gpgkey=https://packagecloud.io/dcommander/turbovnc/gpgkey
https://raw.githubusercontent.com/TurboVNC/repo/main/VGL-GPG-KEY
https://raw.githubusercontent.com/TurboVNC/repo/main/VGL-GPG-KEY-1024
enabled=1
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
metadata_expire=6h
skip_if_unavailable=True
Used Tightvnc back in days of Redhat and a number of Fedora
Core version, then they switch to the tigervnc and that worked for
a long time, then stopped working if local login, with vnc using
wayland/gnome 3. The xfce did work until Fedora 39, and then it
stopped. The stopped supporting the vncserver option, and I could
never get it to work even with xfce. So turbovnc was my only
option. It has worked fine on my test machine, and now on all
machines.
Well, hope you can get something to work either with tigervnc or
turbovnc, but I tried and failed with tigervnc. It worked to 38, but
39 made it impossible. So, looks like you have to do things the
exact tigervnc way with systemd or out of luck.
+------------------------------------------------------------+
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
