Skip to content
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

Closed
sgalke opened this issue Dec 14, 2023 · 19 comments
Closed

vnc completly broken after todays update #174

sgalke opened this issue Dec 14, 2023 · 19 comments

Comments

@sgalke
Copy link

sgalke commented Dec 14, 2023

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....

@sgalke
Copy link
Author

sgalke commented Dec 14, 2023

"todays update" was:

gir1.2-gtk-3.0/stable 1:3.24.38-2deb12u1+rpt3+rpi1 arm64 [aktualisierbar von: 1:3.24.38-2deb12u1+rpt1+rpi1]
gir1.2-handy-1/stable 1.8.1-1+rpt3 arm64 [aktualisierbar von: 1.8.1-1+rpt1]
gtk-update-icon-cache/stable 1:3.24.38-2deb12u1+rpt3+rpi1 arm64 [aktualisierbar von: 1:3.24.38-2deb12u1+rpt1+rpi1]
libgtk-3-0/stable 1:3.24.38-2deb12u1+rpt3+rpi1 arm64 [aktualisierbar von: 1:3.24.38-2deb12u1+rpt1+rpi1]
libgtk-3-common/stable,stable 1:3.24.38-2deb12u1+rpt3+rpi1 all [aktualisierbar von: 1:3.24.38-2deb12u1+rpt1+rpi1]
libhandy-1-0/stable 1.8.1-1+rpt3 arm64 [aktualisierbar von: 1.8.1-1+rpt1]
pixflat-icons/stable,stable 0.23 all [aktualisierbar von: 0.21]
raspi-config/stable,stable 20231214 all [aktualisierbar von: 20231108]
xserver-common/stable,stable 2:21.1.7-3+rpt1+deb12u3 all [aktualisierbar von: 2:21.1.7-3+rpt1+deb12u2]
xserver-xorg-core/stable 2:21.1.7-3+rpt1+deb12u3 arm64 [aktualisierbar von: 2:21.1.7-3+rpt1+deb12u2]

@themicro1
Copy link

themicro1 commented Dec 15, 2023

Same here.
Solution for now:
Create file /etc/xdg/autostart/wayvnc.desktop

[Desktop Entry]
Type=Application
Name=wayvnc
Comment=Start wayvnc
NoDisplay=true
Exec=/usr/bin/wayvnc --render-cursor 
OnlyShowIn=wayfire

Don't use raspi-config until this ist fixed ;)

@sgalke
Copy link
Author

sgalke commented Dec 15, 2023

@themicro1:
folder /home/pi/.config/wayvnc is also missing after fresh installation.
i copied it from a not-already-updated system.
with your (partly) solution and the missing folder (and its contents) vnc is up again.
thank you!

@nithyaatrify
Copy link

Yep, VNC not operational.
Any updates? wayvnc.service does not exist is the error

@XECDesign
Copy link

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?

@nithyaatrify
Copy link

Yep, VNC not operational. Any updates? wayvnc.service does not exist is the error

The legacy version seems to be working fine

@sgalke
Copy link
Author

sgalke commented Dec 15, 2023

The legacy version seems to be working fine

that does not help for rpi models 5.

@spl237
Copy link

spl237 commented Dec 15, 2023

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?

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... ;) )

@apulache
Copy link

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?
Thanks in advance!

@apulache
Copy link

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
raspi-config_20231214_all.deb 2023-12-14 14:40 29K

@sgalke
Copy link
Author

sgalke commented Dec 15, 2023

@nithyaatrify:

tested with fresh install & recomended update:
vnc under legacy wayland does not work. the same missing files / directory. other (minor?) wayland problems: desktop appearance not costomizable, etc ... (no fun, unusable, i am tired now, please test yourself, sorry...)

vnc with wayland turned off under legacy (bullseye) works.

@OwenTea11
Copy link

Same here. Solution for now: Create file /etc/xdg/autostart/wayvnc.desktop

[Desktop Entry]
Type=Application
Name=wayvnc
Comment=Start wayvnc
NoDisplay=true
Exec=/usr/bin/wayvnc --render-cursor 
OnlyShowIn=wayfire

Don't use raspi-config until this ist fixed ;)

Apologies for the noob question but where should I create this file? And is it just a text file?

Thank you!

@hlipnick
Copy link

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 raspi-config_20231214_all.deb 2023-12-14 14:40 29K

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:

  1. Open the temp directory: cd /tmp
  2. Download the .deb file for the old raspi-config: curl -OJL "https://archive.raspberrypi.org/debian/pool/main/r/raspi-config/raspi-config_20231108_all.deb"
  3. Install the old version: sudo apt install ./raspi-config_20231108_all.deb

@sgalke
Copy link
Author

sgalke commented Dec 16, 2023

the latest upgrade raspi_config_20231216 restores at least the status quo ante - vnc is operational again.
there are some minor error left - but no longer completly broken.
thanks!!
issue closed.

@sgalke sgalke closed this as completed Dec 16, 2023
@kventil
Copy link

kventil commented Jan 23, 2024

Ran in the same issue with raspi_config_20240108. The Solution provided by @themicro1 worked for me to get vnc up and running again.

Same here. Solution for now: Create file /etc/xdg/autostart/wayvnc.desktop

[Desktop Entry]
Type=Application
Name=wayvnc
Comment=Start wayvnc
NoDisplay=true
Exec=/usr/bin/wayvnc --render-cursor 
OnlyShowIn=wayfire

Don't use raspi-config until this ist fixed ;)

@lurch
Copy link
Collaborator

lurch commented Jan 24, 2024

@kventil Have you also updated the wayvnc package? Since the last comment in this issue, it has now been updated to be managed by systemd, rather than XDG autostart files.
So could you please try:

  1. sudo rm /etc/xdg/autostart/wayvnc.desktop
  2. sudo reboot
  3. dpkg -l wayvnc
  4. systemctl status wayvnc

Thanks.

@jimmusson
Copy link

The legacy version works fine on pi5 (64 bit)

@kventil
Copy link

kventil commented Jan 25, 2024

@kventil Have you also updated the wayvnc package? Since the last comment in this issue, it has now been updated to be managed by systemd, rather than XDG autostart files. So could you please try:

1. `sudo rm /etc/xdg/autostart/wayvnc.desktop`

2. `sudo reboot`

3. `dpkg -l wayvnc`
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-================================================
ii  wayvnc         0.8.0-rc0-2  arm64        VNC server for wlroots-based Wayland compositors
4. `systemctl status wayvnc`
● wayvnc.service - VNC Server
     Loaded: loaded (/lib/systemd/system/wayvnc.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-01-25 09:39:09 CET; 2s ago
       Docs: man:wayvnc
   Main PID: 6410 (sh)
      Tasks: 6 (limit: 4444)
        CPU: 144ms
     CGroup: /system.slice/wayvnc.service
             ├─6410 /bin/sh /usr/sbin/wayvnc-run.sh
             └─6414 wayvnc --render-cursor --detached --config /etc/wayvnc/config --socket /tmp/wayvnc/wayvncctl.sock

Jan 25 09:39:08 diveramonitor systemd[1]: Starting wayvnc.service - VNC Server...
Jan 25 09:39:09 diveramonitor systemd[1]: Started wayvnc.service - VNC Server.

Looking okay to me. (Have now another issue with wayland but that's unreladted to vnc)

@salasidis
Copy link

salasidis commented Apr 20, 2024

@kventil Have you also updated the wayvnc package? Since the last comment in this issue, it has now been updated to be managed by systemd, rather than XDG autostart files. So could you please try:

  1. sudo rm /etc/xdg/autostart/wayvnc.desktop
  2. sudo reboot
  3. dpkg -l wayvnc
  4. systemctl status wayvnc

Thanks.

I needed to run

systemctl status wayvnc

Then VNC connections were possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests