Re: tigervnc server configuration limitation

2024-02-25 Thread Samuel Sieb
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,

Re: tigervnc server configuration limitation

2024-02-25 Thread Samuel Sieb
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

Re: tigervnc server configuration limitation

2024-02-25 Thread Jonathan Billings
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

Re: tigervnc server configuration limitation

2024-02-25 Thread Roger Heflin
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

Re: tigervnc server configuration limitation

2024-02-25 Thread George N. White III
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

Re: tigervnc server configuration limitation

2024-02-25 Thread Francis . Montagnac
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

Re: tigervnc server configuration limitation

2024-02-25 Thread Francis . Montagnac
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Samuel Sieb
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Francis . Montagnac
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Samuel Sieb
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Samuel Sieb
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Samuel Sieb
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Michael D. Setzer II via users
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Michael D. Setzer II via 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:

Re: tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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: >

Re: tigervnc server configuration limitation

2024-02-24 Thread Francis . Montagnac
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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

Re: tigervnc server configuration limitation

2024-02-24 Thread Michael D. Setzer II via users
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 switc

tigervnc server configuration limitation

2024-02-24 Thread Sam Varshavchik
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