Commenti a: TigerVNC e RealVNC su Raspberry Pi Bookworm OS

Di: roderick young

roderick young — Fri, 11 Oct 2024 01:55:25 +0000

In risposta a hoke.

That sounds like normal behavior for tigervnc, which is based on tightvnc: a new desktop is created.

I was able to get the default desktop by going to raspi-config, making sure that wayfire (wayland) is selected, and enabling vnc. That started wayvnc, which was included in the recommended software of Bookworm for Pi. To view, I needed to use tigervnc on the client. One weakness is that sound is not transmitted to the client by wayvnc, so if you need that, you need to go with X11 plus realvnc, as described in the article.

Di: Barry-IA

Barry-IA — Mon, 20 May 2024 23:09:12 +0000

Probably a hare on the off-topic side of things but for those running their Pi’s headless and Wayland (vs. X11) I found I needed a Dummy Monitor (HDMI version) to remotely view the Desktop. Remember to also purchase a short micro-HDMI to HDMI adapter! Here TigerVNC worked fine once I added the Dummy Monitor.

Di: Tony (aqk)

Tony (aqk) — Sun, 18 Feb 2024 21:38:22 +0000

Please ignore my previous plea for help.
The TigerVNC as well as SSH seems to be running OK again, after I fiddled around with security options and Raspi-config, as well as a couple of reboots.
But then, you KNEW I would eventually get it going, right? 😉
Don’t ask me what the problem was- I have no idea, except that I will not attempt to delete RealVNC again!

Di: Tony (aqk)

Tony (aqk) — Sun, 18 Feb 2024 05:38:29 +0000

Wait! – It gets worse!
I can’t even get a headless session (using PuTTY)
It appears that SSH is down. Any suggestions? ;-(

Di: Tony (aqk)

Tony (aqk) — Sun, 18 Feb 2024 05:27:10 +0000

I had TigerVNC client installed on my Win-11 machine, and have just installed TigerVPN server in my RPi.
It worked great! So I stupidly decided to remove the RealVNC from the Pi.
Now when I try to connect to my Pi, I get the following error:
“Failed to connect to 10…..:5901”
“Unable to connect to socket: no connection could be made because target actively refused it (10061)”
Obviously I deleted more than just RealVNC. How can I restore VNC ?

Di: Lluís J.

Lluís J. — Sat, 03 Feb 2024 14:51:19 +0000

How to keep tigervncserver autorunning after each reboot?
Thanks

Di: piuser99999

piuser99999 — Tue, 30 Jan 2024 01:39:03 +0000

I needed to use RealVNC because I don’t need to open ports or whatever to access the PI remotely, so I had to go back to X11, I hope everything else works fine. But I’m glad that I found this solution after trying on my own to fix RealVNC, thank you. Thank you.

Di: Adam

Adam — Fri, 08 Dec 2023 12:54:13 +0000

In risposta a Diana.

Eigentlich habe ich alles ohne KI geschrieben. Was ist das genaue Problem, Diana?

Di: Diana

Diana — Sun, 03 Dec 2023 16:14:40 +0000

Dieser Artikel hier ist entweder einfach schlecht von KI erstellt oder so mies übersetzt das es nicht zu Ziel führt, es funktioniert einfach nicht nicht mit realvnc noch mit Tigervnc auf einem frisch installiertem Raspberry

Di: pinguino

penguin — Sat, 18 Nov 2023 00:41:21 +0000

So, They have removed and wrecked VNC. Forced us to use crappy tiger-whatever and mangled a workflow I have been using for 9 years. Nice work