I don't run any of my rpi:s with desktops env, but I do run VNC on my desktop machine (KDE though, rpi is gnome right?), and have done quite a few observations over the time.
Does rpiOS use Wayland?
If so, that is probably problem no1. try x11 instead. (I don't even know if xorg is available though)
I feel the client should have less to do with this, and the desktop env or the server is the problem.
You should be able to use any VNC client.
I have to do a whole dance where I find out what value $XAUTHORITY gets, and have to start the server using that so I can connect with a client already at the login manager without having to log in first. (this can be solved with autologin if you are ok with opening up that security hole)
But that seems like something you might not need to do, since it has worked before, but I wanted to mention it if it has something to do with security updates on rpi, things might have changed in that regard.
If this IS the problem, I can spit out a systemd.service you can try, but you should try if changing to x11 works first before starting to mess around with services maybe not needed. (if you are on Wayland)
On a side note, DO NOT EVER UNDER ANY CIRCUMSTANCES NEGLECT TO UPDATE YOUR SYSTEM BECAUSE "IT MIGHT BREAK"!!!!!
If this is the case, YOU ARE USING A BROKEN SYSTEM!!!
ALWAYS ALWAYS ALWAYS run updates, YOU NEED THE SECURITY PATCHES!!!
You can run a system without updating it, but NEVER EVER EVER EVER let it connect to the internet!!!
A system without security patches can become infected in SECONDS if you are really unlucky, I'm dead serious here!
Does rpiOS use Wayland?
If so, that is probably problem no1. try x11 instead. (I don't even know if xorg is available though)
I feel the client should have less to do with this, and the desktop env or the server is the problem.
You should be able to use any VNC client.
I have to do a whole dance where I find out what value $XAUTHORITY gets, and have to start the server using that so I can connect with a client already at the login manager without having to log in first. (this can be solved with autologin if you are ok with opening up that security hole)
But that seems like something you might not need to do, since it has worked before, but I wanted to mention it if it has something to do with security updates on rpi, things might have changed in that regard.
If this IS the problem, I can spit out a systemd.service you can try, but you should try if changing to x11 works first before starting to mess around with services maybe not needed. (if you are on Wayland)
On a side note, DO NOT EVER UNDER ANY CIRCUMSTANCES NEGLECT TO UPDATE YOUR SYSTEM BECAUSE "IT MIGHT BREAK"!!!!!
If this is the case, YOU ARE USING A BROKEN SYSTEM!!!
ALWAYS ALWAYS ALWAYS run updates, YOU NEED THE SECURITY PATCHES!!!
You can run a system without updating it, but NEVER EVER EVER EVER let it connect to the internet!!!
A system without security patches can become infected in SECONDS if you are really unlucky, I'm dead serious here!
Statistics: Posted by bedna — Thu May 09, 2024 7:35 am