Re: tigervnc server configuration limitation
On 2/25/24 05:17, Roger Heflin wrote: 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. For some reason, he wants a second separate session, not controlling the existing session. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 2/25/24 06:35, Jonathan Billings wrote: What this means is there’s no TCP port listening for Xvnc, just a UNIX socket file. So two people or a local and remote session can’t have sessions interfering with each other. I played with using systemd socket activation too but that’s too complicated for this post. Then, for remote connections, I would forward the UNIX socket with SSH. If you are using a VNC client that doesn’t support UNIX sockets, you can tell OpenSSH to forward a remote socket to a local TCP socket, but you can also forward a remote to local socket to use with tigervnc’s client in Fedora. The great thing about it is that there’s never a listening tcp port on either side of the connection except ssh. When it’s set up, it’s just like having a remote VNC session with the upstream systemd units, but it doesn’t need a listening TCP port assigned to each user. It's a valid option, but I don't see how it's relevant to this issue. There's no port conflict. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On Feb 25, 2024, at 02:23, Samuel Sieb wrote: > > On 2/24/24 23:17, francis.montag...@inria.fr wrote: >>> It does have something to do with running from systemd, but I have no >>> idea what it is. >> Not sure at all of that. It seems to be instead an compatibility between >> vncsession and startxfce4. > > 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. I wish I had access to my internal git account I have at work, but I discovered that both OpenSSH and Xvnc support using UNIX sockets instead of listening on a port. What this means is that you can have your systemd service (I ran as a user, enabling linger) uses a socket file (I used one in XDG_RUNTIME_DIR because it’s private) when launching Xvnc by specifying `−rfbunixpath path` in the parameters to Xvnc. I think this is only available in somewhat recent TigerVNC, so it doesn’t work in Centos 7. What this means is there’s no TCP port listening for Xvnc, just a UNIX socket file. So two people or a local and remote session can’t have sessions interfering with each other. I played with using systemd socket activation too but that’s too complicated for this post. Then, for remote connections, I would forward the UNIX socket with SSH. If you are using a VNC client that doesn’t support UNIX sockets, you can tell OpenSSH to forward a remote socket to a local TCP socket, but you can also forward a remote to local socket to use with tigervnc’s client in Fedora. The great thing about it is that there’s never a listening tcp port on either side of the connection except ssh. When it’s set up, it’s just like having a remote VNC session with the upstream systemd units, but it doesn’t need a listening TCP port assigned to each user. Honestly, I kinda wish the TigerVNC project would just adopt this for their provided units. Maybe they can’t because Windows can’t use UNIX sockets? I wonder if the Windows 10 OpenSSH can forward sockets to a local tcp socket? (I’m not a windows user) -- Jonathan Billings -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
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 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@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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 -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On Sat, Feb 24, 2024 at 11:11 AM Sam Varshavchik 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. > With systemd, configured VNC Servers are started at boot, so unless you are adding new users without configuring VNC, you shouldn't need to start a server from a GUI session. I find, however, that I rarely need VNC as web-based remote systems (e.g., Rstudio server, Jupyter) meet my needs. -- George N. White III -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On Sun, 25 Feb 2024 09:11:34 +0100 francis.montag...@inria.fr wrote: >> 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. 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 -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On Sat, 24 Feb 2024 23:23:28 -0800 Samuel Sieb wrote: > On 2/24/24 23:17, francis.montag...@inria.fr wrote: >>> It does have something to do with running from systemd, but I have no >>> idea what it is. >> Not sure at all of that. It seems to be instead an compatibility between >> vncsession and startxfce4. > 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. Right: I did my test being not logged in (at the console). It fails also with xfcetest, thus the startxfce4 script is not the culprit. xfce failed for me yesterday with a different message in the log: Starting desktop session xfce Unrecognized option: -xsession use: X [:] [option] but today it works (while being not logged in). > If the user is logged in and you start it from the command line, it also > works. Right, from a terminal of the main session with: sudo /usr/libexec/vncsession-start :1 > 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. Being logged in with fluxbox and starting a fluxbox VNC session works also. -- francis -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 2/24/24 23:17, francis.montag...@inria.fr wrote: It does have something to do with running from systemd, but I have no idea what it is. Not sure at all of that. It seems to be instead an compatibility between vncsession and startxfce4. 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. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On Sat, 24 Feb 2024 20:11:20 -0800 Samuel Sieb wrote: > On 2/24/24 08:52, Sam Varshavchik wrote: >> ... 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. > 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.) Right, because /usr/sbin/vncsession (a binary) called from the /usr/libexec/vncsession-start script by the vncserver@.service does a: xinit /etc/X11/xinit/Xsession COMMAND -- /usr/bin/Xvnc :1 OPTIONS where COMMAND is the command specified in the Exec= option of the /usr/share/xsessions/SESSION.desktop file. For xfce, this is startxfce4 that print the "X server already running..." message if DISPLAY is set and do not call then xinit itself. It would be worth to trace this script to know precisely what happens. No courage to do that at the moment :-( I made the following test that works for me: replace startxfce4 by xfce4-session: - make a new session /usr/share/xsessions/xfcetest.desktop with: [Desktop Entry] Version=1.0 Name=XfceTest Session Exec=xfce4-session Icon= Type=Application DesktopNames=XFCETEST - declare session=xfcetest in ~/.vnc/config Can you try it ? I do that on a minimal Fedora machine having only xfce4 as sessions. The initial test I made with session=xfce4 worked may be because, since this xfce4 session doesn't exist, vncsession switched to the only existing session (xfce) and in a different way that worked. In addition, I installed fluxbox and it works with vncsession. > It does have something to do with running from systemd, but I have no > idea what it is. Not sure at all of that. It seems to be instead an compatibility between vncsession and startxfce4. -- francis -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 2/24/24 08:52, Sam Varshavchik wrote: ... 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. 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. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
Samuel Sieb writes: On 2/24/24 08:52, Sam Varshavchik wrote: Sam Varshavchik writes: But something is still broken. I went through the motions, set session=xfce, but then something is still broken with systemd. systemctl start vncserver@: 1 results in: Feb 24 11:30:33 monster.email-scan.com systemd[1]: Starting vncserver@: 1.service - Remote desktop service (VNC)… Feb 24 11:30:34 monster.email-scan.com systemd[1]: Started vncserver@: 1.service - Remote desktop service (VNC). Feb 24 11:30:35 monster.email-scan.com systemd[1]: vncserver@:1.service: Deactivated successfully. That's it, no further diagnostics, and nothing is listening on port 5901. ... 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. 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. They are different ports. I just verified that DISPLAY in the VNC session is :1.0 On the system console it's :0.0, of course. Yet, I cannot start both of them, on Fedora, if both are running xfce. This is a documented limitation, in the package's HOWTO. I run a VNC server with openbox using systemd and it works fine. Now, try getting your VNC server up with an existing graphical session already running. It won't work, if both are XFCE (or if both are gnome, as I understand it). pgpSeJtYcoqr5.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
Samuel Sieb writes: On 2/24/24 07:10, Sam Varshavchik 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. I don't see how that would work on Ubuntu either. If there's already a session for a user, creating another session is going to cause great confusion and weird happenings. 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 18831846 0 10:00 ?00:00:00 xfce4-session mrsam 54115408 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' pgpnhKR7moWaE.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 2/24/24 08:52, Sam Varshavchik wrote: Sam Varshavchik writes: But something is still broken. I went through the motions, set session=xfce, but then something is still broken with systemd. systemctl start vncserver@:1 results in: Feb 24 11:30:33 monster.email-scan.com systemd[1]: Starting vncserver@:1.service - Remote desktop service (VNC)… Feb 24 11:30:34 monster.email-scan.com systemd[1]: Started vncserver@:1.service - Remote desktop service (VNC). Feb 24 11:30:35 monster.email-scan.com systemd[1]: vncserver@:1.service: Deactivated successfully. That's it, no further diagnostics, and nothing is listening on port 5901. ... 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. 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. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 2/24/24 07:10, Sam Varshavchik 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. I don't see how that would work on Ubuntu either. If there's already a session for a user, creating another session is going to cause great confusion and weird happenings. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 24 Feb 2024 at 16:55, Sam Varshavchik wrote: From: Sam Varshavchik To: Community support for Fedora users Subject:Re: tigervnc server configuration limitation Date sent: Sat, 24 Feb 2024 16:55:05 -0500 Send reply to: Community support for Fedora users > 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/$bas earch 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/SRP MS 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:mi...@guam.net mailto:msetze...@gmail.com mailto:msetze...@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
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. pgpwOSNjUBDvk.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
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 To: Community support for Fedora users Subject:Re: tigervnc server configuration limitation Date sent: Sat, 24 Feb 2024 15:10:33 -0500 Send reply to: Community support for Fedora users > francis.montag...@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
Re: tigervnc server configuration limitation
francis.montag...@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. pgpc2PZETLi54.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
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. -- francis -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
Sam Varshavchik writes: Michael D. Setzer II via users writes: On 24 Feb 2024 at 10:10, Sam Varshavchik wrote: > 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. 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. Oh, this is a Gnome thing? That's not a problem for me, since I use XFCE anyway. But something is still broken. I went through the motions, set session=xfce, but then something is still broken with systemd. systemctl start vncserver@: 1 results in: Feb 24 11:30:33 monster.email-scan.com systemd[1]: Starting vncserver@: 1.service - Remote desktop service (VNC)… Feb 24 11:30:34 monster.email-scan.com systemd[1]: Started vncserver@: 1.service - Remote desktop service (VNC). Feb 24 11:30:35 monster.email-scan.com systemd[1]: vncserver@:1.service: Deactivated successfully. That's it, no further diagnostics, and nothing is listening on port 5901. ... 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. pgpy7hatLW1Sd.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
Michael D. Setzer II via users writes: On 24 Feb 2024 at 10:10, Sam Varshavchik wrote: > 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. 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. Oh, this is a Gnome thing? That's not a problem for me, since I use XFCE anyway. But something is still broken. I went through the motions, set session=xfce, but then something is still broken with systemd. systemctl start vncserver@: 1 results in: Feb 24 11:30:33 monster.email-scan.com systemd[1]: Starting vncserver@:1.service - Remote desktop service (VNC)… Feb 24 11:30:34 monster.email-scan.com systemd[1]: Started vncserver@:1.service - Remote desktop service (VNC). Feb 24 11:30:35 monster.email-scan.com systemd[1]: vncserver@:1.service: Deactivated successfully. That's it, no further diagnostics, and nothing is listening on port 5901. pgp2v2G40O1Ap.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc server configuration limitation
On 24 Feb 2024 at 10:10, Sam Varshavchik wrote:
From: Sam Varshavchik
To: Fedora Users List
Subject:tigervnc server configuration limitation
Date sent: Sat, 24 Feb 2024 10:10:42 -0500
Send reply to: Community support for Fedora users
> 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.
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
>
> This is not a limitation on Ubuntu. It's too bad that Fedora cannot do the
> same.
>
>
++
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mi...@guam.net
mailto:msetze...@gmail.com
mailto:msetze...@gmx.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
++
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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
tigervnc server configuration limitation
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. pgpTJ7TgBL2l0.pgp Description: PGP signature -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/15/23 09:03, Barry Scott wrote: What do you get when you do the following commands: rpm -ql rpm-libs dnf list installed rpm-libs I am on FC39 now and I forced updated dnf to the fc39 version $ rpm -ql rpm-libs /usr/lib/.build-id /usr/lib/.build-id/a8 /usr/lib/.build-id/a8/ad83daa16d97f5c842e86a70f9e51cbe02094f /usr/lib/.build-id/ec /usr/lib/.build-id/ec/1c5daeb02d49221df9e4c206be1825dc361f4a /usr/lib64/librpm.so.10 /usr/lib64/librpm.so.10.0.0 /usr/lib64/librpmio.so.10 /usr/lib64/librpmio.so.10.0.0 /usr/lib64/rpm-plugins ~$ dnf list installed rpm-libs Installed Packages rpm-libs.x86_64 4.19.0-1.fc39 @fedora Are you running the ARM version of fedora? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/15/23 10:28, Jeffrey Walton wrote: `dnf repolist enabled` may be helpful: $ dnf repolist enabled repo idrepo name fedora Fedora 39 - x86_64 fedora-cisco-openh264 Fedora 39 OpenH264 (from Cisco) - x86_64 updatesFedora 39 - x86_64 - Updates But it looks like they are stock in F39: $ dnf whatprovides 'librpmio.so*' rpm-libs-4.19.0-1.fc39.i686 : Libraries for manipulating RPM packages Repo: fedora Matched from: Provide: librpmio.so.10 rpm-libs-4.19.0-1.fc39.x86_64 : Libraries for manipulating RPM packages Repo: @System Matched from: Provide: librpmio.so.10()(64bit) rpm-libs-4.19.0-1.fc39.x86_64 : Libraries for manipulating RPM packages Repo: fedora Matched from: Provide: librpmio.so.10()(64bit) Jeff Keep in mind that dnf system-upgrade download --refresh --releasever=39 failed to update me to the fc39 version of dnf. When I forced the issue, things worked fine. But first I had to get dnf working, which is why the 9--> 10 links. Download grade to fc38 version of dnf before running all your tests ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On Wed, Nov 15, 2023 at 12:04 PM Barry Scott wrote: > > On 15 Nov 2023, at 16:18, ToddAndMargo via users > wrote: > > I had the same as you until today when I did a `dnf upgrade`. > Then all hell broke loose and librpmio and librpm got upgraded > to 10. > > On my f38 system there is no .10 > > # dnf install /usr/lib64/librpm.so.10 > Last metadata expiration check: 3:43:48 ago on Wed 15 Nov 2023 13:16:33 GMT. > No match for argument: /usr/lib64/librpm.so.10 > Error: Unable to find a match: /usr/lib64/librpm.so.10 > > What do you get when you do the following commands: > > rpm -ql rpm-libs > dnf list installed rpm-libs > > This is what I see: > > [root@armf38 ~]# rpm -ql rpm-libs > /usr/lib/.build-id > /usr/lib/.build-id/1a > /usr/lib/.build-id/1a/eb222329842e6fb62cf39efa961713445a579e > /usr/lib/.build-id/7b > /usr/lib/.build-id/7b/c93dcd84e2911ac9ce66e44543f2ece1d30a53 > /usr/lib64/librpm.so.9 > /usr/lib64/librpm.so.9.4.0 > /usr/lib64/librpmio.so.9 > /usr/lib64/librpmio.so.9.4.0 > /usr/lib64/rpm-plugins > [root@armf38 ~]# dnf list installed rpm-libs > Installed Packages > rpm-libs.aarch644.18.1-3.fc38 > @updates > [root@armf38 ~]# > > I am especially interested in the repo that your .so.10 came from. > My .so.9 came from @updates. `dnf repolist enabled` may be helpful: $ dnf repolist enabled repo idrepo name fedora Fedora 39 - x86_64 fedora-cisco-openh264 Fedora 39 OpenH264 (from Cisco) - x86_64 updatesFedora 39 - x86_64 - Updates But it looks like they are stock in F39: $ dnf whatprovides 'librpmio.so*' rpm-libs-4.19.0-1.fc39.i686 : Libraries for manipulating RPM packages Repo: fedora Matched from: Provide: librpmio.so.10 rpm-libs-4.19.0-1.fc39.x86_64 : Libraries for manipulating RPM packages Repo: @System Matched from: Provide: librpmio.so.10()(64bit) rpm-libs-4.19.0-1.fc39.x86_64 : Libraries for manipulating RPM packages Repo: fedora Matched from: Provide: librpmio.so.10()(64bit) Jeff ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
> On 15 Nov 2023, at 16:18, ToddAndMargo via users > wrote: > > I had the same as you until today when I did a `dnf upgrade`. > Then all hell broke loose and librpmio and librpm got upgraded > to 10. On my f38 system there is no .10 # dnf install /usr/lib64/librpm.so.10 Last metadata expiration check: 3:43:48 ago on Wed 15 Nov 2023 13:16:33 GMT. No match for argument: /usr/lib64/librpm.so.10 Error: Unable to find a match: /usr/lib64/librpm.so.10 What do you get when you do the following commands: rpm -ql rpm-libs dnf list installed rpm-libs This is what I see: [root@armf38 ~]# rpm -ql rpm-libs /usr/lib/.build-id /usr/lib/.build-id/1a /usr/lib/.build-id/1a/eb222329842e6fb62cf39efa961713445a579e /usr/lib/.build-id/7b /usr/lib/.build-id/7b/c93dcd84e2911ac9ce66e44543f2ece1d30a53 /usr/lib64/librpm.so.9 /usr/lib64/librpm.so.9.4.0 /usr/lib64/librpmio.so.9 /usr/lib64/librpmio.so.9.4.0 /usr/lib64/rpm-plugins [root@armf38 ~]# dnf list installed rpm-libs Installed Packages rpm-libs.aarch644.18.1-3.fc38 @updates [root@armf38 ~]# I am especially interested in the repo that your .so.10 came from. My .so.9 came from @updates. Barry ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On Tue, Nov 14, 2023 at 9:07 PM ToddAndMargo via users wrote: On 11/14/23 18:47, ToddAndMargo via users wrote: On Tue, Nov 14, 2023 at 6:40 PM ToddAndMargo via users wrote: On 11/14/23 16:37, Joe Zeff wrote: On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: How do I fix this? You might try just removing tigervnc and letting it remove the no-longer needed dependencies. dnf is giving me the same output for any command I give it. On 11/14/23 17:19, Roger Heflin wrote: > lrwxrwxrwx. 1 root root 15 Apr 24 2023 /usr/lib64/librpm.so.9 -> > librpm.so.9.4.0 > -rwxr-xr-x. 1 root root 551368 Apr 24 2023 /usr/lib64/librpm.so.9.4.0 > > so > cd /usr/lib64 > ln -s librpm.so.9.4.0 librpm.so.9 > > Assuming the librpm.so.9.4.0 is still there. But if that link is > missing there is a decent chance that other links and/or files are > also gone. > # ls -al librpm.so* lrwxrwxrwx. 1 root root 16 Sep 18 17:00 librpm.so.10 -> librpm.so.10.0.0 -rwxr-xr-x. 1 root root 563032 Sep 18 17:00 librpm.so.10.0.0 Hmmm ... Okay, I got dnf to work again with the following: /usr/lib64# ln -s librpmio.so.10.0.0 librpmio.so.9 /usr/lib64# ln -s librpm.so.10.0.0 librpm.so.9 Now how do I fix it right? Just posted: dnf looking for outdated librpmio and librpm https://bugzilla.redhat.com/show_bug.cgi?id=2249732 On 11/15/23 08:02, Roger Heflin wrote: > It would have to be some sort of package problem. Unless something > specifically deleted that so.9 link (which seems unlikely). > > Clearly dnf thinks it needs so.9 but you only have so.10 > > I just upgraded my fc38 machine and have so.9 and this rpm version. > > What fedora version do you have and what rpm do you have? > > rpm -qa --filesbypkg | grep -i librpm.so > rpm-libs /usr/lib64/librpm.so.9 > rpm-libs /usr/lib64/librpm.so.9.4.0 > rpm -qa | grep -i rpm-libs > rpm-libs-4.18.1-3.fc38.x86_64 > I had the same as you until today when I did a `dnf upgrade`. Then all hell broke loose and librpmio and librpm got upgraded to 10. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
It would have to be some sort of package problem. Unless something specifically deleted that so.9 link (which seems unlikely). Clearly dnf thinks it needs so.9 but you only have so.10 I just upgraded my fc38 machine and have so.9 and this rpm version. What fedora version do you have and what rpm do you have? rpm -qa --filesbypkg | grep -i librpm.so rpm-libs /usr/lib64/librpm.so.9 rpm-libs /usr/lib64/librpm.so.9.4.0 rpm -qa | grep -i rpm-libs rpm-libs-4.18.1-3.fc38.x86_64 On Tue, Nov 14, 2023 at 9:07 PM ToddAndMargo via users wrote: > > On 11/14/23 18:47, ToddAndMargo via users wrote: > > > >> > >> > >> On Tue, Nov 14, 2023 at 6:40 PM ToddAndMargo via users > >> wrote: > >>> > >>> On 11/14/23 16:37, Joe Zeff wrote: > >>>> On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: > >>>>> > >>>>> How do I fix this? > >>>> > >>>> You might try just removing tigervnc and letting it remove the > >>>> no-longer > >>>> needed dependencies. > >>> > >>> dnf is giving me the same output for any command I give it. > > > > On 11/14/23 17:19, Roger Heflin wrote: > > > lrwxrwxrwx. 1 root root 15 Apr 24 2023 /usr/lib64/librpm.so.9 -> > > > librpm.so.9.4.0 > > > -rwxr-xr-x. 1 root root 551368 Apr 24 2023 /usr/lib64/librpm.so.9.4.0 > > > > > > so > > > cd /usr/lib64 > > > ln -s librpm.so.9.4.0 librpm.so.9 > > > > > > Assuming the librpm.so.9.4.0 is still there. But if that link is > > > missing there is a decent chance that other links and/or files are > > > also gone. > > > > > > > # ls -al librpm.so* > > lrwxrwxrwx. 1 root root 16 Sep 18 17:00 librpm.so.10 -> > > librpm.so.10.0.0 > > -rwxr-xr-x. 1 root root 563032 Sep 18 17:00 librpm.so.10.0.0 > > > > > > Hmmm ... > > > > Okay, > > I got dnf to work again with the following: > > /usr/lib64# ln -s librpmio.so.10.0.0 librpmio.so.9 > /usr/lib64# ln -s librpm.so.10.0.0 librpm.so.9 > > Now how do I fix it right? > > Just posted: > dnf looking for outdated librpmio and librpm > https://bugzilla.redhat.com/show_bug.cgi?id=2249732 > > > > > > > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/14/23 19:06, ToddAndMargo via users wrote: On 11/14/23 18:47, ToddAndMargo via users wrote: On Tue, Nov 14, 2023 at 6:40 PM ToddAndMargo via users wrote: On 11/14/23 16:37, Joe Zeff wrote: On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: How do I fix this? You might try just removing tigervnc and letting it remove the no-longer needed dependencies. dnf is giving me the same output for any command I give it. On 11/14/23 17:19, Roger Heflin wrote: > lrwxrwxrwx. 1 root root 15 Apr 24 2023 /usr/lib64/librpm.so.9 -> > librpm.so.9.4.0 > -rwxr-xr-x. 1 root root 551368 Apr 24 2023 /usr/lib64/librpm.so.9.4.0 > > so > cd /usr/lib64 > ln -s librpm.so.9.4.0 librpm.so.9 > > Assuming the librpm.so.9.4.0 is still there. But if that link is > missing there is a decent chance that other links and/or files are > also gone. > # ls -al librpm.so* lrwxrwxrwx. 1 root root 16 Sep 18 17:00 librpm.so.10 -> librpm.so.10.0.0 -rwxr-xr-x. 1 root root 563032 Sep 18 17:00 librpm.so.10.0.0 Hmmm ... Okay, I got dnf to work again with the following: /usr/lib64# ln -s librpmio.so.10.0.0 librpmio.so.9 /usr/lib64# ln -s librpm.so.10.0.0 librpm.so.9 Now how do I fix it right? Just posted: dnf looking for outdated librpmio and librpm https://bugzilla.redhat.com/show_bug.cgi?id=2249732 dnf was still on FC38. The real fix: # dnf upgrade dnf --releasever=39 Failed on its # dnf upgrade --releasever=39 3000+ file later, # dnf upgrade dnf --releasever=39 --best --allowerasing 273 files later, and # rpm -qa dnf dnf-4.18.1-1.fc39.noarch Fixed ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/14/23 18:47, ToddAndMargo via users wrote: On Tue, Nov 14, 2023 at 6:40 PM ToddAndMargo via users wrote: On 11/14/23 16:37, Joe Zeff wrote: On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: How do I fix this? You might try just removing tigervnc and letting it remove the no-longer needed dependencies. dnf is giving me the same output for any command I give it. On 11/14/23 17:19, Roger Heflin wrote: > lrwxrwxrwx. 1 root root 15 Apr 24 2023 /usr/lib64/librpm.so.9 -> > librpm.so.9.4.0 > -rwxr-xr-x. 1 root root 551368 Apr 24 2023 /usr/lib64/librpm.so.9.4.0 > > so > cd /usr/lib64 > ln -s librpm.so.9.4.0 librpm.so.9 > > Assuming the librpm.so.9.4.0 is still there. But if that link is > missing there is a decent chance that other links and/or files are > also gone. > # ls -al librpm.so* lrwxrwxrwx. 1 root root 16 Sep 18 17:00 librpm.so.10 -> librpm.so.10.0.0 -rwxr-xr-x. 1 root root 563032 Sep 18 17:00 librpm.so.10.0.0 Hmmm ... Okay, I got dnf to work again with the following: /usr/lib64# ln -s librpmio.so.10.0.0 librpmio.so.9 /usr/lib64# ln -s librpm.so.10.0.0 librpm.so.9 Now how do I fix it right? Just posted: dnf looking for outdated librpmio and librpm https://bugzilla.redhat.com/show_bug.cgi?id=2249732 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On Tue, Nov 14, 2023 at 6:40 PM ToddAndMargo via users wrote: On 11/14/23 16:37, Joe Zeff wrote: On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: How do I fix this? You might try just removing tigervnc and letting it remove the no-longer needed dependencies. dnf is giving me the same output for any command I give it. On 11/14/23 17:19, Roger Heflin wrote: > lrwxrwxrwx. 1 root root 15 Apr 24 2023 /usr/lib64/librpm.so.9 -> > librpm.so.9.4.0 > -rwxr-xr-x. 1 root root 551368 Apr 24 2023 /usr/lib64/librpm.so.9.4.0 > > so > cd /usr/lib64 > ln -s librpm.so.9.4.0 librpm.so.9 > > Assuming the librpm.so.9.4.0 is still there. But if that link is > missing there is a decent chance that other links and/or files are > also gone. > # ls -al librpm.so* lrwxrwxrwx. 1 root root 16 Sep 18 17:00 librpm.so.10 -> librpm.so.10.0.0 -rwxr-xr-x. 1 root root 563032 Sep 18 17:00 librpm.so.10.0.0 Hmmm ... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
lrwxrwxrwx. 1 root root 15 Apr 24 2023 /usr/lib64/librpm.so.9 -> librpm.so.9.4.0 -rwxr-xr-x. 1 root root 551368 Apr 24 2023 /usr/lib64/librpm.so.9.4.0 so cd /usr/lib64 ln -s librpm.so.9.4.0 librpm.so.9 Assuming the librpm.so.9.4.0 is still there. But if that link is missing there is a decent chance that other links and/or files are also gone. On Tue, Nov 14, 2023 at 6:40 PM ToddAndMargo via users wrote: > > On 11/14/23 16:37, Joe Zeff wrote: > > On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: > >> > >> How do I fix this? > > > > You might try just removing tigervnc and letting it remove the no-longer > > needed dependencies. > > dnf is giving me the same output for any command I give it. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/14/23 16:39, ToddAndMargo via users wrote: On 11/14/23 16:16, ToddAndMargo via users wrote: Hi All, How do I fix this? Many thanks, -T # rpm -qa tiger\* tigervnc-license-1.13.1-6.fc38.noarch tigervnc-icons-1.13.1-6.fc38.noarch tigervnc-1.13.1-6.fc38.x86_64 # dnf remove tigervnc-1.13.1-6.fc38.x86_64 tigervnc-icons-1.13.1-6.fc38.noarch tigervnc-license-1.13.1-6.fc38.noarch Traceback (most recent call last): File "/usr/bin/dnf", line 61, in from dnf.cli import main File "/usr/lib/python3.12/site-packages/dnf/__init__.py", line 30, in import dnf.base File "/usr/lib/python3.12/site-packages/dnf/base.py", line 29, in import libdnf.transaction File "/usr/lib64/python3.12/site-packages/libdnf/__init__.py", line 14, in from . import conf File "/usr/lib64/python3.12/site-packages/libdnf/conf.py", line 10, in from . import _conf ImportError: librpm.so.9: cannot open shared object file: No such file or directory Seems like this is a nnf issue. This give the same output: # dnf whatprovides libplist I removed tigervnc with rpm. Now I am trying to fix dnf ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/14/23 16:37, Joe Zeff wrote: On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: How do I fix this? You might try just removing tigervnc and letting it remove the no-longer needed dependencies. dnf is giving me the same output for any command I give it. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/14/23 16:16, ToddAndMargo via users wrote: Hi All, How do I fix this? Many thanks, -T # rpm -qa tiger\* tigervnc-license-1.13.1-6.fc38.noarch tigervnc-icons-1.13.1-6.fc38.noarch tigervnc-1.13.1-6.fc38.x86_64 # dnf remove tigervnc-1.13.1-6.fc38.x86_64 tigervnc-icons-1.13.1-6.fc38.noarch tigervnc-license-1.13.1-6.fc38.noarch Traceback (most recent call last): File "/usr/bin/dnf", line 61, in from dnf.cli import main File "/usr/lib/python3.12/site-packages/dnf/__init__.py", line 30, in import dnf.base File "/usr/lib/python3.12/site-packages/dnf/base.py", line 29, in import libdnf.transaction File "/usr/lib64/python3.12/site-packages/libdnf/__init__.py", line 14, in from . import conf File "/usr/lib64/python3.12/site-packages/libdnf/conf.py", line 10, in from . import _conf ImportError: librpm.so.9: cannot open shared object file: No such file or directory Seems like this is a nnf issue. This give the same output: # dnf whatprovides libplist ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc won't remove
On 11/14/2023 05:16 PM, ToddAndMargo via users wrote: How do I fix this? You might try just removing tigervnc and letting it remove the no-longer needed dependencies. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
tigervnc won't remove
Hi All, How do I fix this? Many thanks, -T # rpm -qa tiger\* tigervnc-license-1.13.1-6.fc38.noarch tigervnc-icons-1.13.1-6.fc38.noarch tigervnc-1.13.1-6.fc38.x86_64 # dnf remove tigervnc-1.13.1-6.fc38.x86_64 tigervnc-icons-1.13.1-6.fc38.noarch tigervnc-license-1.13.1-6.fc38.noarch Traceback (most recent call last): File "/usr/bin/dnf", line 61, in from dnf.cli import main File "/usr/lib/python3.12/site-packages/dnf/__init__.py", line 30, in import dnf.base File "/usr/lib/python3.12/site-packages/dnf/base.py", line 29, in import libdnf.transaction File "/usr/lib64/python3.12/site-packages/libdnf/__init__.py", line 14, in from . import conf File "/usr/lib64/python3.12/site-packages/libdnf/conf.py", line 10, in from . import _conf ImportError: librpm.so.9: cannot open shared object file: No such file or directory ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc fails with "Cannot establish any listening sockets - Make sure an X server isn't already running(EE)"
On 1/13/23 18:58, Jonathan Billings wrote: On Jan 13, 2023, at 21:45, Alex wrote: vncserver[5803]: Could not start Xvnc. vncserver[5803]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running vncserver[5803]: (EE) vncserver[5803]: Fatal server error: vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) vncserver[5803]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running vncserver[5803]: (EE) vncserver[5803]: Fatal server error: vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) systemd[1]: vncserver@:1.service: Control process exited, code=exited, status=255/EXCEPTION systemd[1]: vncserver@:1.service: Failed with result 'exit-code'. systemd[1]: Failed to start vncserver@:1.service - Remote desktop service (VNC). Could missing fonts really cause this? What more can I do to troubleshoot this? The font thing is a warning. (See where it says WARNING) You missed the errors: vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running There’s already something listening on the port it is trying to run on. Perhaps take a look at what port it is listening on and fix that. Or possibly it just can't open that port. Check the journal for selinux messages or anything else. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: tigervnc fails with "Cannot establish any listening sockets - Make sure an X server isn't already running(EE)"
On Jan 13, 2023, at 21:45, Alex wrote: > > > Hi, > I have a fedora37 desktop install with tigervnc-server and can't get it to > start. I'd like it to start on system boot. > > I've followed the HOWTO.md as well as numerous examples online, and can't > figure out what's wrong. I've set the vncpasswd for the user listed in > vncserver.users. > > /etc/tigervnc/vncserver.users: > :1=gary > > $ cat ~/.vnc/config|grep -Ev '^$|^#' > session=gnome > securitytypes=vncauth,tlsvnc > geometry=800x600 > > # systemctl start vncserver@:1 > Job for vncserver@:1.service failed because the control process exited with > error code. > See "systemctl status vncserver@:1.service" and "journalctl -xeu > vncserver@:1.service" for details. > > systemd[1]: Starting vncserver@:1.service - Remote desktop service (VNC)... > vncserver[5803]: WARNING: vncserver has been replaced by a systemd unit and > is now considered deprecated and removed in upstream. > vncserver[5803]: Please read /usr/share/doc/tigervnc/HOWTO.md for more > information. > vncserver[5803]: WARNING: The first attempt to start Xvnc failed, possibly > because the font > vncserver[5803]: catalog is not properly configured. Attempting to determine > an appropriate > vncserver[5803]: font path for this system and restart Xvnc using that font > path ... > vncserver[5803]: Could not start Xvnc. > vncserver[5803]: _XSERVTransSocketUNIXCreateListener: > ...SocketCreateListener() failed > vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running > vncserver[5803]: (EE) > vncserver[5803]: Fatal server error: > vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an X > server isn't already running(EE) > vncserver[5803]: _XSERVTransSocketUNIXCreateListener: > ...SocketCreateListener() failed > vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running > vncserver[5803]: (EE) > vncserver[5803]: Fatal server error: > vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an X > server isn't already running(EE) > systemd[1]: vncserver@:1.service: Control process exited, code=exited, > status=255/EXCEPTION > systemd[1]: vncserver@:1.service: Failed with result 'exit-code'. > systemd[1]: Failed to start vncserver@:1.service - Remote desktop service > (VNC). > > Could missing fonts really cause this? What more can I do to troubleshoot > this? The font thing is a warning. (See where it says WARNING) You missed the errors: > vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running There’s already something listening on the port it is trying to run on. Perhaps take a look at what port it is listening on and fix that. -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
tigervnc fails with "Cannot establish any listening sockets - Make sure an X server isn't already running(EE)"
Hi, I have a fedora37 desktop install with tigervnc-server and can't get it to start. I'd like it to start on system boot. I've followed the HOWTO.md as well as numerous examples online, and can't figure out what's wrong. I've set the vncpasswd for the user listed in vncserver.users. /etc/tigervnc/vncserver.users: :1=gary $ cat ~/.vnc/config|grep -Ev '^$|^#' session=gnome securitytypes=vncauth,tlsvnc geometry=800x600 # systemctl start vncserver@:1 Job for vncserver@:1.service failed because the control process exited with error code. See "systemctl status vncserver@:1.service" and "journalctl -xeu vncserver@:1.service" for details. systemd[1]: Starting vncserver@:1.service - Remote desktop service (VNC)... vncserver[5803]: WARNING: vncserver has been replaced by a systemd unit and is now considered deprecated and removed in upstream. vncserver[5803]: Please read /usr/share/doc/tigervnc/HOWTO.md for more information. vncserver[5803]: WARNING: The first attempt to start Xvnc failed, possibly because the font vncserver[5803]: catalog is not properly configured. Attempting to determine an appropriate vncserver[5803]: font path for this system and restart Xvnc using that font path ... vncserver[5803]: Could not start Xvnc. vncserver[5803]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running vncserver[5803]: (EE) vncserver[5803]: Fatal server error: vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) vncserver[5803]: _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already running vncserver[5803]: (EE) vncserver[5803]: Fatal server error: vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) systemd[1]: vncserver@:1.service: Control process exited, code=exited, status=255/EXCEPTION systemd[1]: vncserver@:1.service: Failed with result 'exit-code'. systemd[1]: Failed to start vncserver@:1.service - Remote desktop service (VNC). Could missing fonts really cause this? What more can I do to troubleshoot this? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
[SOLVED] tigervnc: Attempted to configure an invalid screen layout
On Thu, 23 Dec 2021 19:49:08 +0100 Frank Elsner via users wrote: > Hello, > > I've problems to connect to an vnc server. Tigervnc dies with the message > > Attempted to configure an invalid screen layout The UltraVNC on the server was replaced by an updated version. Now it works. --Frank ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: TigerVNC fails to display new windows properly
On Sun, 2019-05-19 at 14:23 -0400, Alex wrote: > The reason the hostname is displayed as "localhost.localdomain" is > because it's on a private IP range (192.168.9.110) without DNS, and > I'm using port forwarding from the cable modem to this host for port > 5900 through 6000. I'm not sure if VNC will handle localhost being its hostname, it will depend on how smart it is, or whether it bothers using hostnames. localhost, and localhost.localdomain will normally resolve back to 127.0.0.1 (meaning "itself"). As such, connections may not get put through to the remote side of things. While some things will also add the local IP address to that line in the /etc/hosts file, that can cause failures. The machine's hostname should resolve to its real IP (the one that other devices can reach it at). You don't need to have a DNS server to resolve hostnames. You can add it yourself to your /etc/hosts file (of course, you need to have a fixed IP for this to be consistent). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: TigerVNC fails to display new windows properly
On 5/19/19 11:23 AM, Alex wrote: Here is the command I run on the local machine to start the vncserver as the regular user (gary): $ vncserver :1 -geometry 800x600 -depth 24 Try running "export DISPLAY=:1" before that. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
TigerVNC fails to display new windows properly
Hi, I've installed tigervnc according to the instructions here for a new fedora30 install: https://www.server-world.info/en/note?os=Fedora_28&p=desktop&f=6 mate-desktop doesn't seem to work properly, so I've just stuck with the default xinitrc, which produces the default fedora30 desktop. I can connect to the remote machine after providing authorization, then the local authorization at least twice and finally getting to the remote desktop. It appears as it normally does, with "Activities" in the upper-left. The problem is that after starting any applications, whether it's the file manager, Firefox, or a regular terminal, it starts, but the app does not appear. I believe it's being directed to another display. Is that possible? I've started the application, and I can confirm it's running by connecting to the machine via ssh and finding it in the process list, but it just doesn't display on the remote desktop. I don't have physical access to the machine to see if the app is started on the default desktop. Here is my ~/.vnc/xstartup: $ cat xstartup #!/bin/sh unset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS exec /etc/X11/xinit/xinitrc #exec /usr/bin/mate-session Here is the log file that is produced after starting vncserver: $ cat localhost.localdomain\:1.log Xvnc TigerVNC 1.9.0 - built Feb 3 2019 09:54:51 Copyright (C) 1999-2018 TigerVNC Team and many others (see README.rst) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 12003000, The X.Org Foundation Thu May 16 20:28:43 2019 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5901 vncext: created VNC server for screen 0 Thu May 16 20:28:47 2019 ComparingUpdateTracker: 0 pixels in / 0 pixels out ComparingUpdateTracker: (1:-nan ratio) Thu May 16 20:29:02 2019 Connections: accepted: 68.195.199.42::37586 SConnection: Client needs protocol version 3.8 SConnection: Client requests security type VeNCrypt(19) SVeNCrypt: Client requests security type TLSVnc (258) VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 Here is the command I run on the local machine to start the vncserver as the regular user (gary): $ vncserver :1 -geometry 800x600 -depth 24 Here is what the vncserver command shows in the process table: $ ps ax|grep vnc 6991 pts/5Sl 0:05 /usr/bin/Xvnc :1 -auth /home/gary/.Xauthority -depth 24 -desktop localhost.localdomain:1 (gary) -fp catalogue:/etc/X11/fontpath.d -geometry 800x600 -pn -rfbauth /home/gary/.vnc/passwd -rfbport 5901 -rfbwait 3 The reason the hostname is displayed as "localhost.localdomain" is because it's on a private IP range (192.168.9.110) without DNS, and I'm using port forwarding from the cable modem to this host for port 5900 through 6000. Ideas greatly appreciated. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Unable to bring TigerVNC server to get a remote display of other than the default 1024x768 in FC25
On 06/27/2017 03:59 PM, Ed Greshko wrote: What I believe is that the vncviewer is doing is requesting 1024x768 and that is what you'll get. Now, the "interesting" or bad thing is that once you connect at a lower resolution than what you want Xvnc will stick with it no matter what you do from the viewer side. So Try disconnecting, restart the server, and then use "vncviewer -geometry 1600x1200 hostname:1" to connect. In other words, once you connect with a given resolution you're stuck to it on subsequent connections. :-( I was surprised to discover that xrandr works with Xvnc. I had initially started the vnc server at 1024x768 as a convenient default. But checking with xrandr showed that long list of options and changing the mode worked and is persistent on future connections. I use Remmina, but I expect vncviewer would work the same. If not, Remmina works well and handles a wide variety of protocols and connection options. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Unable to bring TigerVNC server to get a remote display of other than the default 1024x768 in FC25
On 06/28/17 01:46, Walter H. wrote: > On 27.06.2017 19:23, Walter H. wrote: >> xrandr only shows >> >> Screen 0: minimum 32 x 32, current 1024 x 768, maximum 32768 x 32768 >> VNC-0 connected primary 1024x768+0+0 0mm x 0mm >>1600x1200 60.00 + >>1920x1200 60.00 >>1920x1080 60.00 >>1680x1050 60.00 >>1400x1050 60.00 >>1360x768 60.00 >>1280x1024 60.00 >>1280x960 60.00 >>1280x800 60.00 >>1280x720 60.00 >>1024x768 60.00* >>800x600 60.00 >>640x480 60.00 >> >> /etc/systemd/system/vncserver@.service >> has this >> ExecStart=/usr/bin/vncserver %i -geometry 1600x1200 >> >> and ~/.vnc/config >> has this >> geometry=1600x1200 >> >> and still connected with 1024x768 ... even when setting SELINUX to permissive >> why? >> >> the goal is either 1600x1200 or 1280x1024, the default 1024x768 is too small >> >> Thanks, >> Walter > strange thing > > when I'm connected and on a terminal I can enter the following > > xrandr -s 1280x1024 > or > xrandr -s 1600x1200 > or > xrandr -s 1920x1200 > > and the display changes to this resolution on the fly > > how can I bring the system to do this before I connect via vncviewer from my > other > box? A couple of things The 1600x1200 60.00 + in your xrandr output indicates what the Xserver, in this case Xvnc, is offering as the optimal resolution and 1024x768 60.00* (with the *) is what you've connected at. But I think you already knew that. I just like typing. What I believe is that the vncviewer is doing is requesting 1024x768 and that is what you'll get. Now, the "interesting" or bad thing is that once you connect at a lower resolution than what you want Xvnc will stick with it no matter what you do from the viewer side. So Try disconnecting, restart the server, and then use "vncviewer -geometry 1600x1200 hostname:1" to connect. In other words, once you connect with a given resolution you're stuck to it on subsequent connections. :-( -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Unable to bring TigerVNC server to get a remote display of other than the default 1024x768 in FC25
On 27.06.2017 19:23, Walter H. wrote: xrandr only shows Screen 0: minimum 32 x 32, current 1024 x 768, maximum 32768 x 32768 VNC-0 connected primary 1024x768+0+0 0mm x 0mm 1600x1200 60.00 + 1920x1200 60.00 1920x1080 60.00 1680x1050 60.00 1400x1050 60.00 1360x768 60.00 1280x1024 60.00 1280x960 60.00 1280x800 60.00 1280x720 60.00 1024x768 60.00* 800x600 60.00 640x480 60.00 /etc/systemd/system/vncserver@.service has this ExecStart=/usr/bin/vncserver %i -geometry 1600x1200 and ~/.vnc/config has this geometry=1600x1200 and still connected with 1024x768 ... even when setting SELINUX to permissive why? the goal is either 1600x1200 or 1280x1024, the default 1024x768 is too small Thanks, Walter strange thing when I'm connected and on a terminal I can enter the following xrandr -s 1280x1024 or xrandr -s 1600x1200 or xrandr -s 1920x1200 and the display changes to this resolution on the fly how can I bring the system to do this before I connect via vncviewer from my other box? Thanks, Walter smime.p7s Description: S/MIME Cryptographic Signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Unable to bring TigerVNC server to get a remote display of other than the default 1024x768 in FC25
On 26.06.2017 05:10, Ed Greshko wrote: On 06/26/17 01:19, Walter H. wrote: Hello, I did nearly the same as here https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-TigerVNC.html#s3-configuring-vnc-server by the way this ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024" must be ExecStart=/usr/bin/vncserver %i -geometry 1280x1024 because the 'runuser'-variant doesn't work at all, no connection possible from VNCviewer; or is there also something missing in the SELinux policies? the -geometry parameter is ignored, I only get a display of 1024x768 when connecting with VNCviewer from other machine ... FWIW. My /etc/systemd/system/vncserver@.service contains... ExecStart=/usr/bin/vncserver %i -geometry 1920x1080 The running process shows egreshko 839 1 0 11:01 ?00:00:03 /usr/bin/Xvnc :1 -geometry 1920x1080 -auth /home/egreshko/.Xauthority -desktop f25f.greshko.com:1 (egreshko) -fp catalogue:/etc/X11/fontpath.d -httpd /usr/share/vnc/classes -pn -rfbauth /home/egreshko/.vnc/passwd -rfbport 5901 -rfbwait 3 how do you get this output? And when I connect via vncviewer from another system I get the following output from xrandr Screen 0: minimum 32 x 32, current 1920 x 1080, maximum 32768 x 32768 VNC-0 connected primary 1920x1080+0+0 0mm x 0mm 1920x1080 60.00*+ 1920x1200 60.00 1600x1200 60.00 1680x1050 60.00 1400x1050 60.00 1360x768 60.00 1280x1024 60.00 1280x960 60.00 1280x800 60.00 1280x720 60.00 1024x768 60.00 800x600 60.00 640x480 60.00 I also happen to set my ~/.vnc/config file to that geometry as a habit. xrandr only shows Screen 0: minimum 32 x 32, current 1024 x 768, maximum 32768 x 32768 VNC-0 connected primary 1024x768+0+0 0mm x 0mm 1600x1200 60.00 + 1920x1200 60.00 1920x1080 60.00 1680x1050 60.00 1400x1050 60.00 1360x768 60.00 1280x1024 60.00 1280x960 60.00 1280x800 60.00 1280x720 60.00 1024x768 60.00* 800x600 60.00 640x480 60.00 /etc/systemd/system/vncserver@.service has this ExecStart=/usr/bin/vncserver %i -geometry 1600x1200 and ~/.vnc/config has this geometry=1600x1200 and still connected with 1024x768 ... even when setting SELINUX to permissive why? the goal is either 1600x1200 or 1280x1024, the default 1024x768 is too small Thanks, Walter smime.p7s Description: S/MIME Cryptographic Signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Unable to bring TigerVNC server to get a remote display of other than the default 1024x768 in FC25
On 06/26/17 01:19, Walter H. wrote: > Hello, > > I did nearly the same as here > https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-TigerVNC.html#s3-configuring-vnc-server > > > by the way this > ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024" > > must be > ExecStart=/usr/bin/vncserver %i -geometry 1280x1024 > > because the 'runuser'-variant doesn't work at all, no connection possible from > VNCviewer; > > or is there also something missing in the SELinux policies? > > the -geometry parameter is ignored, I only get a display of 1024x768 when > connecting with VNCviewer from other machine ... > FWIW. My /etc/systemd/system/vncserver@.service contains... ExecStart=/usr/bin/vncserver %i -geometry 1920x1080 The running process shows egreshko 839 1 0 11:01 ?00:00:03 /usr/bin/Xvnc :1 -geometry 1920x1080 -auth /home/egreshko/.Xauthority -desktop f25f.greshko.com:1 (egreshko) -fp catalogue:/etc/X11/fontpath.d -httpd /usr/share/vnc/classes -pn -rfbauth /home/egreshko/.vnc/passwd -rfbport 5901 -rfbwait 3 And when I connect via vncviewer from another system I get the following output from xrandr Screen 0: minimum 32 x 32, current 1920 x 1080, maximum 32768 x 32768 VNC-0 connected primary 1920x1080+0+0 0mm x 0mm 1920x1080 60.00*+ 1920x1200 60.00 1600x1200 60.00 1680x1050 60.00 1400x1050 60.00 1360x768 60.00 1280x1024 60.00 1280x960 60.00 1280x800 60.00 1280x720 60.00 1024x768 60.00 800x600 60.00 640x480 60.00 I also happen to set my ~/.vnc/config file to that geometry as a habit. -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Unable to bring TigerVNC server to get a remote display of other than the default 1024x768 in FC25
Hello, I did nearly the same as here https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-TigerVNC.html#s3-configuring-vnc-server by the way this ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024" must be ExecStart=/usr/bin/vncserver %i -geometry 1280x1024 because the 'runuser'-variant doesn't work at all, no connection possible from VNCviewer; or is there also something missing in the SELinux policies? the -geometry parameter is ignored, I only get a display of 1024x768 when connecting with VNCviewer from other machine ... Thanks, Walter smime.p7s Description: S/MIME Cryptographic Signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Flickering Desktop with tigervnc-1.5.0 on Fedora-23
Hello, When using tigervnc 1.5.0 server on fedora 23 workstation with tigervnc 1.5.0 viewer on windows 7 (both 64bit) I can see the desktop. But it quickly flickers between the following view fragments in undeterministic order: * full login screen * Background image * black screen * just buttons, * just password text input I can login somehow. But after login it happens the same. Only additionally the desktop is among the flickering fragments. It seems to work in general. I can open programs but it still flickers heavily. It makes no difference whether I use it in window or full screen mode (2 monitors in my case). I have tried the fedora 23 installation on a bare metal server and on a vmware virtual machine with exactly the same problem. Tigervnc 1.4.3 (server & viewer) fedora 22 and fedora 22 kde spin worked very well in my setup. So it seems not to by client side issue. -- Leslie -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F18: TigerVnc incomplete?
On 11/30/2013 12:50 PM, Dan Thurman wrote: What's up with TigerVnc? It seems to be missing the Ctrl-Alt-Del icon and other icons for Windoes? If there is another VncClient that has it, what would it be? Ahh... memory lapse! I forgot about 'F8' key! Sorry for the noise! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F18: TigerVnc incomplete?
What's up with TigerVnc? It seems to be missing the Ctrl-Alt-Del icon and other icons for Windoes? If there is another VncClient that has it, what would it be? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: tigervnc
> yum search vnc, if you can't see it, add rpmfusion, look..., you can see vnc4server and others things more, but i recommended vino and vinagre. I tried searching with yum. And trying to find repos for fedora has been a little difficult. Thanks for pointing to rpmfusion.. Vino is fine for sharing the desktop if someone is logged onto the console, but if it's a headless server no one is ever logged on. You have to have a vncserver for that. It turns out the long pause at login was caused by a very slow drawing of the background graphic (that default fedora 14 blue one) I ended up installing gconf-editor, and then just turning off that unlock pop-up, and the background screen, and also desktop animations. No sense in having to enter my password twice, anyway. Tigervnc is fast enough if I use the ultravnc client. Thanks! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: tigervnc
2011/1/29, compdoc : > I have tigervnc server installed on a fedora 14 box, and when I use the > Windows tigervnc client it is terribly slow. > > Normally, I use the ultravnc windows client which is very fast, however when > I use it to connect to the tigervnc server, there is a long pause with a > black screen before the unlock popup comes up. > > I think this is happening because the client and server are negotiating > which encoding to use. But I might be completely wrong. > > After I log in, everything is fine - screen updates are fast and it works as > it should. But if I let it idle, the screen blacks out again and the long > pause occurs before the login prompt. > > Does anyone know how to prevent the long pause, or even better, where I can > find vnc4server (Xvnc4) for fedora? Does it exist in some repo somewhere? > > Vnc4server is very fast and doesn't have these pause issues. > > Thanks for any help... I tried remote control on fedora 14 with vino server and vinagre client, it was very good, but if you want vnc server you can try search: yum search vnc, if yuo can't see it, add rpmfusion, look..., you can see vnc4server and others things more, but i recommended vino and vinagre. In windows you can use vnc viewer, for me ti was good... > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > -- Edguit@r http://cybernautape.blogspot.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
tigervnc
I have tigervnc server installed on a fedora 14 box, and when I use the Windows tigervnc client it is terribly slow. Normally, I use the ultravnc windows client which is very fast, however when I use it to connect to the tigervnc server, there is a long pause with a black screen before the unlock popup comes up. I think this is happening because the client and server are negotiating which encoding to use. But I might be completely wrong. After I log in, everything is fine - screen updates are fast and it works as it should. But if I let it idle, the screen blacks out again and the long pause occurs before the login prompt. Does anyone know how to prevent the long pause, or even better, where I can find vnc4server (Xvnc4) for fedora? Does it exist in some repo somewhere? Vnc4server is very fast and doesn't have these pause issues. Thanks for any help... -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Anaconda is insisting on installing TigerVNC-Server for dependencies
On 9/4/2010 10:56 AM, Tim wrote: > On Sat, 2010-09-04 at 07:33 -0400, Claude Jones wrote: >> > I didn't know anaconda was no longer necessary > As far as I were aware, it never was. It's the installer, it's not used > post-installation. I guess I never fully understood what it did - I somehow had the idea it was involved in detection of hardware - apparently, I had that somewhat wrong. This, from the fedoraproject.org/wiki/Anaconda page is what I remembered: "During installation, a target computer's hardware is identified and configured and the appropriate file systems for the system's architecture are created." I had an imperfect recollection of this role and had assumed it was something needed in the event new hardware was added to a system...I guess that latter assumption doesn't follow from the quote. -- Claude Jones Brunswick, MD, USA -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Anaconda is insisting on installing TigerVNC-Server for dependencies
On Sat, 2010-09-04 at 07:33 -0400, Claude Jones wrote: > I didn't know anaconda was no longer necessary As far as I were aware, it never was. It's the installer, it's not used post-installation. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Anaconda is insisting on installing TigerVNC-Server for dependencies
On 9/3/2010 2:53 AM, Hiisi wrote: > Because there's an option for remote installation through VNC. But as > Matthew already asked you, why do you need anaconda at all? Thanks Matthew and Hiisi for your replies. Due to other issues affecting email the past two days, I've been slow with this reply. I didn't know anaconda was no longer necessary - I hadn't installed it purposefully and was under the assumption that it had been installed with my initial set of default packages when I installed Fedora. I seem to remember it being a vital part of the OS at one time and just assumed I should try to reinstall it when it was removed during my removal of TigerVNC-server... -- Claude Jones Brunswick, MD, USA -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Anaconda is insisting on installing TigerVNC-Server for dependencies
2010/9/3 Claude Jones : > I removed tigervnc-server the other day to install RealVNC enterprise. I > noticed while removing tigervnc that it also uninstalled Anaconda which > seemed very strange. I just tried to reinstall Anaconda and it wants to > reinstall Tigervnc-server for dependencies, but, if I try to do that, it > conflicts with RealVNC server - anyone else seeing this? > > This is on Fedora 13 x64 with all the latest updates > > -- > > Claude Jones > > Brunswick, MD, USA > Because there's an option for remote installation through VNC. But as Matthew already asked you, why do you need anaconda at all? -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Anaconda is insisting on installing TigerVNC-Server for dependencies
On Thu, Sep 02, 2010 at 09:46:41PM -0400, Claude Jones wrote: > I removed tigervnc-server the other day to install RealVNC > enterprise. I noticed while removing tigervnc that it also > uninstalled Anaconda which seemed very strange. I just tried to > reinstall Anaconda and it wants to reinstall Tigervnc-server for > dependencies, but, if I try to do that, it conflicts with RealVNC > server - anyone else seeing this? Why do you want anaconda installed? -- Matthew Miller Senior Systems Architect -- Instructional & Research Computing Services Harvard School of Engineering & Applied Sciences -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Anaconda is insisting on installing TigerVNC-Server for dependencies
I removed tigervnc-server the other day to install RealVNC enterprise. I noticed while removing tigervnc that it also uninstalled Anaconda which seemed very strange. I just tried to reinstall Anaconda and it wants to reinstall Tigervnc-server for dependencies, but, if I try to do that, it conflicts with RealVNC server - anyone else seeing this? This is on Fedora 13 x64 with all the latest updates -- Claude Jones Brunswick, MD, USA-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
