Dear neilgl,
Thanks for your reply.
I have a spare micro SD which already has the Raspberry PI OS in it. I was using this micro SD card before, but the issue is it's only 8GB, so I barely have any space left to do anything, which is annoying![:lol:]( "Laughing")
I did what you suggested with this spare micro SD card, and Tiger VNC does connect to my Raspberry PI (without doing any updates)! Therefore, I believe I have identified the issue. Indeed when switching micro SD cards, I noticed that wayvnc and neatvnc versions were different. Spare micro SD has wayvnc and neatvnc both at version 0.9-dev, whereas new micro SD has version 0.9.1 for both packages. Do you agree with the assumption of the new version being the issue? Do you suggest anyway to revert wayvnc and neatvnc to this previous 0.9-dev version? I presume I upgraded all packages at some point when messing with the new micro SD, and for the spare micro SD I didn't perform upgrades.
The official Debian repository only has wayvnc and neatvnc versions 0.5.0 and 0.9.1 (https://tracker.debian.org/pkg/wayvnc and https://tracker.debian.org/pkg/neatvnc). Version 0.5.0 seems to be too old and 0.9.1 is the one causing the issue for me.
I think I have been able to pinpoint the tag of this 0.9-dev version for wayvnc and neatvnc packages as tag v0.9.0-rc0, on both respective repositories (https://github.com/any1/wayvnc/tree/v0.9.0-rc0 and https://github.com/any1/neatvnc/tree/v0.9.0-rc0). So I could try purging wayvnc and neatvnc from my Raspberry PI in order to manually build these versions from the repository, although I don't really trust my skills, so if there were another option that would be much better.
Many thanks.
Thanks for your reply.
I have a spare micro SD which already has the Raspberry PI OS in it. I was using this micro SD card before, but the issue is it's only 8GB, so I barely have any space left to do anything, which is annoying
I did what you suggested with this spare micro SD card, and Tiger VNC does connect to my Raspberry PI (without doing any updates)! Therefore, I believe I have identified the issue. Indeed when switching micro SD cards, I noticed that wayvnc and neatvnc versions were different. Spare micro SD has wayvnc and neatvnc both at version 0.9-dev, whereas new micro SD has version 0.9.1 for both packages. Do you agree with the assumption of the new version being the issue? Do you suggest anyway to revert wayvnc and neatvnc to this previous 0.9-dev version? I presume I upgraded all packages at some point when messing with the new micro SD, and for the spare micro SD I didn't perform upgrades.
The official Debian repository only has wayvnc and neatvnc versions 0.5.0 and 0.9.1 (https://tracker.debian.org/pkg/wayvnc and https://tracker.debian.org/pkg/neatvnc). Version 0.5.0 seems to be too old and 0.9.1 is the one causing the issue for me.
I think I have been able to pinpoint the tag of this 0.9-dev version for wayvnc and neatvnc packages as tag v0.9.0-rc0, on both respective repositories (https://github.com/any1/wayvnc/tree/v0.9.0-rc0 and https://github.com/any1/neatvnc/tree/v0.9.0-rc0). So I could try purging wayvnc and neatvnc from my Raspberry PI in order to manually build these versions from the repository, although I don't really trust my skills, so if there were another option that would be much better.
Many thanks.
Statistics: Posted by camalazeon — Wed Jul 23, 2025 10:03 pm