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, no
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 complicate
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 start
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
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 sam
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 av
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
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 th
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 c
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
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.co
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 s
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
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 i
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
tur
ort 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 Sa
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/s
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 o
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
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
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
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/ad83daa16d
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
updates
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
>
> #
> 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 expirat
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?
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 r
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 ju
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
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
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 dec
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
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 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.noarc
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 em
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
vncser
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
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
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
> 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 sharin
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
>
42 matches
Mail list logo
