DietPi-Software | Remove RealVNC #6881
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MichaIng
added a commit
that referenced
this pull request
Jan 22, 2024
- RealVNC | Support for RealVNC for Raspberry Pi has been removed from Raspberry Pi Ltd. end, who are suggesting to use TigerVNC instead, which we support already: https://www.raspberrypi.com/documentation/computers/remote-access.html#vnc. While the APT packages are still present and generally work with X11 (https://help.realvnc.com/hc/en-us/articles/14110635000221-Raspberry-Pi-5-Bookworm-and-RealVNC-Connect), they depend on legacy GPU API libraries, which have been deprecated and are not provided anymore by the new kernel and firmware packages for RPi. Since we need to migrate to the new kernel/firmware stack for Raspberry Pi 5 support, we need to drop support for RealVNC as well. If you have installed it currently, it will continue to work for now, but we suggest to migrate to TigerVNC. See the following instructions about how to uninstall RealVNC manually: #6881
MichaIng
added a commit
that referenced
this pull request
Feb 1, 2024
- RealVNC | Support for RealVNC for Raspberry Pi has been removed from Raspberry Pi Ltd. end, who are suggesting to use TigerVNC instead, which we support already: https://www.raspberrypi.com/documentation/computers/remote-access.html#vnc. While the APT packages are still present and generally work with X11 (https://help.realvnc.com/hc/en-us/articles/14110635000221-Raspberry-Pi-5-Bookworm-and-RealVNC-Connect), they depend on legacy GPU API libraries, which have been deprecated and are not provided anymore by the new kernel and firmware packages for RPi. Since we need to migrate to the new kernel/firmware stack for Raspberry Pi 5 support, we need to drop support for RealVNC as well. If you have installed it currently, it will continue to work for now, but we suggest to migrate to TigerVNC. See the following instructions about how to uninstall RealVNC manually: #6881
|
Okay, RealVNC actually still/again works very well on Bookworm, with and without KMS enabled. It does not depend on the legacy libraries anymore. The problem hence really seems for RPi OS that it does not support Wayland, but that is not an issue for us, as we support both. I'll just split the software install/uninstall steps and services/scripts and keep RealVNC otherwise. |
- RealVNC | Support for RealVNC for Raspberry Pi has been removed from Raspberry Pi Ltd. end, who are suggesting to use TigerVNC instead, which we support already: https://www.raspberrypi.com/documentation/computers/remote-access.html#vnc. While the APT packages are still present and generally work with X11 (https://help.realvnc.com/hc/en-us/articles/14110635000221-Raspberry-Pi-5-Bookworm-and-RealVNC-Connect), they depend on legacy GPU API libraries, which have been deprecated and are not provided anymore by the new kernel and firmware packages for RPi. Since we need to migrate to the new kernel/firmware stack for Raspberry Pi 5 support, we need to drop support for RealVNC as well. If you have installed it currently, it will continue to work for now, but we suggest to migrate to TigerVNC. See the following instructions about how to uninstall RealVNC manually: #6881
|
Instead of splitting the config code, for now I cleaned if up and structured it a little: 187a21f |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of the information from RealVNC themselves, before merging this, I want to verify whether the package provided by the RPi Bookworm suite really depends on the legacy APIs. My RPi 5 arrives tomorrow 😄, will test it then.
Since the uninstaller for RealVNC has been removed as well, to uninstall it manually:
systemctl disable --now vncserver-{x11-serviced,virtuald,vncserver} rm -Rf /etc/systemd/system/vncserver-{x11-serviced,virtuald,vncserver}.d /usr/local/bin/vncserver /etc/systemd/system/vncserver.service apt autopurge realvnc-vnc-serverTo install TigerVNC as replacement: