TigerVNC / tigervnc

High performance, multi-platform VNC client and server
https://tigervnc.org
GNU General Public License v2.0
4.85k stars 907 forks source link

TigerVNC Doesn't Currently Run Under MacOS Sequoia #1764

Open takuhii opened 3 weeks ago

takuhii commented 3 weeks ago

Describe the bug Doesn't work on MacOS Sequoia Dev Beta (24A5264n)

To Reproduce Steps to reproduce the behavior: Open TigerVNC on Sequoia, just freezes and beachballs

Expected behavior Expect TigerVNC to run

Screenshots

Screenshot 2024-06-14 at 11 00 32

Notice here how the button stays depressed, can't capture the cursor, but the cursor beachballs the whole time Tiger is running.

Screenshot 2024-06-14 at 11 01 47

Then it goes straight to this prompt, no moaning about certificates (which it usually does)...

Client (please complete the following information):

Server (please complete the following information):

Additional context Updated to TigerVNC 1.13.80, same result...

CendioOssman commented 3 weeks ago

Given that it's a beta of macOS, it might simply be a bug there.

The fact that it is unresponsive whilst connecting is a known limitation, though. And given the error message, it might simply be a network issue. Can other VNC clients connect to that server from that macOS machine?

takuhii commented 2 weeks ago

Yes, RealVNC works fine.

CendioOssman commented 2 weeks ago

Can you do a packet trace for a connection attempt by TigerVNC? E.g. tcpdump on the server.

takuhii commented 2 weeks ago

Can you advise on how I would do this? I am on a Mac

CendioOssman commented 2 weeks ago

I'm afraid I'm not familiar with what tools might exist on macOS for this. But you can do it on the server side as well. Run the following:

$ sudo tcpdump -i any port 5900

And let us know what it says.

takuhii commented 2 weeks ago

Hi, I just get this...

tcpdump: data link type PKTAP
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type PKTAP (Apple DLT_PKTAP), snapshot length 524288 bytes
10:30:44.084859 IP 192.168.1.234.58697 > host81-141-190-37.range81-141.btcentralplus.com.rfb: Flags [S], seq 693010272, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 4209233816 ecr 0,sackOK,eol], length 0
10:31:16.084723 IP 192.168.1.234.58697 > host81-141-190-37.range81-141.btcentralplus.com.rfb: Flags [S], seq 693010272, win 65535, options [mss 1460,sackOK,eol], length 0
10:31:38.151104 IP 192.168.1.234.58845 > host81-141-190-37.range81-141.btcentralplus.com.rfb: Flags [SEWA], seq 734493188, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 3450298448 ecr 0,sackOK,eol], length 0
10:31:39.151581 IP 192.168.1.234.58845 > host81-141-190-37.range81-141.btcentralplus.com.rfb: Flags [SEWA], seq 734493188, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 3450299448 ecr 0,sackOK,eol], length 0
10:31:40.150894 IP 192.168.1.234.58845 > host81-141-190-37.range81-141.btcentralplus.com.rfb: Flags [S], seq 734493188, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 3450300448 ecr 0,sackOK,eol], length 0
CendioOssman commented 2 weeks ago

That shows some network issue between macOS and Raspbian, which is outside our control. :/

Could you do the same dump using RealVNC and include the first few packages? It should have the same issue, so it would be good to see what differs.