I am just a newbie and installed DietPi with LXDE on RPi 3B+ yesterday. I have been trying to use RealVNC in shared desktop mode but failed. RealVNC is running ok if I set SOFTWARE_VNCSERVER_SHARE_DESKTOP=0 in /boot/dietpi.txt. However, if I set it to 1, RealVNC fails to connect from my notebook to RPi. My RPi is connected to a TV and is used as a HTPC. I really need to get shared mode working to gain control from my notebook.
BTW, how do I zoom out the desktop? I’ve changed overscan parameters in /boot/config.txt, but it has no effect.
The display options in dietpi-config, overscan can be turned on and left right up down overscans can be adjusted. However, this adjustment can not change the size of the desktop, so icons are off the desktop partially.
BTW, the overscan parameters can only be changed once from dietpi-config. This must be a bug. I need to edit /boot/config.txt to get them changed after the first change.
A VNC client shows an overscan issue? Very strange, I though this can only happen on an actual physical screen which does not have 1x1 pixel mapping, hence nowadays a rare phenomena that overscan is required at all. And a VNC client is no physical screen.
I just tested to change overscan settings back and forth multiple times without issues. How to you estimate whether it worked or not? Do you see the output on the screen (in scrollback buffer) when subsequently re-setting the individual overscan values? And does the menu show the changes?
I changed AutoStart Desktop to Local Terminal first and rebooted. Then I ran DietPi-Config from the terminal and changed AutoStart back to Desktop and rebooted again.
Ah sorry for the misunderstanding about overscan and VNC.
Strange indeed. You mean you changed overscan settings when booting into terminal? As if for some reason the change didn’t apply when doing from within a desktop session. What is true is that dietpi-config requires root permissions, though it should tell you so when trying to call with a different user. However good that it works now. Probably the desktop/X server itself somehow invalidated overscan, like it does with resolution when you change via desktop GUI settings.
Very strange, I though this can only happen on an actual physical screen which does not have 1x1 pixel mapping, hence nowadays a rare phenomena that overscan is required at all. And a VNC client is no physical screen.