The "remote_server" is a remote server that is used by many users at the same time. Now, when I run "vncserver -localhost no -geometry 3840x2160" command to try to start my own VNC server session with a system-assigned display ID (hopefully), I got the following error:
========= start of messages on the screen ==========
Warning: remote_server:17 is taken because of /tmp/.X17-lock
Remove this file if there is no X server remote_server:17
Warning: remote_server:18 is taken because of /tmp/.X18-lock
Remove this file if there is no X server remote_server:18
WARNING: The first attempt to start Xvnc failed, possibly because the font
catalog is not properly configured. Attempting to determine an appropriate
font path for this system and restart Xvnc using that font path ...
Could not start Xvnc.
Unrecognized option: no
use: X [:<display>] [option]
-a # default pointer acceleration (factor)
-ac disable access control restrictions
-audit int set audit trail level
-auth file select authorization file
... ...
========= end of messages on the screen ==========
Files /tmp/.X17-lock and
/tmp/.X18-lock are files created by other user which I don't have permission to delete. The display :17 and :18 may be legally being used by the user, or the VNC server was crashed for this user, I don't know. I don't have the intention to take display :17 and :18; it's ok to let it be. There are still tons of display IDs
available for me to use in the system. So my question is: how to have the vncserver bypass the display IDs being occupied, automatically assigns one to me that is available (I don't mind what number it is), and start the VNC server without errors so that I can proceed with my work in the GUI gnome desktop? I have searched Internet but didn't find any solution that is applicable to me.