-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vnc completly broken after todays update #174
Comments
"todays update" was: gir1.2-gtk-3.0/stable 1:3.24.38-2 |
Same here.
Don't use raspi-config until this ist fixed ;) |
@themicro1: |
Yep, VNC not operational. |
I think the issue is that we shipped RPi-Distro/raspi-config#226 without having the pre-requisites for it in place. @spl237 Is that something that's ready to go, or do we need to revert that PR merge? |
The legacy version seems to be working fine |
that does not help for rpi models 5. |
As far as I know, those changes aren't ready yet, so that change will need to be reverted for now. (I didn't realise you were going to release it... ;) ) |
I can confirmed that the solution proposed here didn't work on Raspberry Pi 5, any instructions to remove the packages causing the issues or revert back? |
Here is a temporal fix for Raspberry Pi 5 using Raspberry Pi OS, it worked for me.
Be aware not to update raspi-config at least we know this version cause the problems |
tested with fresh install & recomended update: vnc with wayland turned off under legacy (bullseye) works. |
Apologies for the noob question but where should I create this file? And is it just a text file? Thank you! |
This worked perfectly on a new Raspberry Pi 5. Thank you! Also just adding for anyone not familiar with installing .deb files, this worked for me:
|
the latest upgrade raspi_config_20231216 restores at least the status quo ante - vnc is operational again. |
Ran in the same issue with raspi_config_20240108. The Solution provided by @themicro1 worked for me to get vnc up and running again.
|
@kventil Have you also updated the
Thanks. |
The legacy version works fine on pi5 (64 bit) |
Looking okay to me. (Have now another issue with wayland but that's unreladted to vnc) |
I needed to run
Then VNC connections were possible |
vnc is no longer operational, neither real-vnc nor wayvnc.
bookworm 32-bit and 64-bit, hardware 4b, 5b
raspi-config reports red-colored errors :
Failed to stop wayvnc.service: Unit wayvnc.service not loaded.
Failed to enable unit: Unit file wayvnc.service does not exist.
fresh install did not help. same desaster after update....
The text was updated successfully, but these errors were encountered: