Look at desktop numbers in this sequence (cut and paste): they are not coerent. cloc3@wlan0 ~ $ vncserver :3 New 'X' desktop is wlan0:1 Starting applications specified in /home/cloc3/.vnc/xstartup Log file is /home/cloc3/.vnc/wlan0:1.log cloc3@wlan0 ~ $ vncserver :1 New 'X' desktop is wlan0:2 Starting applications specified in /home/cloc3/.vnc/xstartup Log file is /home/cloc3/.vnc/wlan0:2.log cloc3@wlan0 ~ $ ls /tmp/.X*-lock -t /tmp/.X1-lock /tmp/.X3-lock /tmp/.X0-lock cloc3@wlan0 ~ $ vncserver -kill :3 Can't find file /home/cloc3/.vnc/wlan0:3.pid You'll have to kill the Xvnc process manually cloc3@wlan0 ~ $ vncserver -kill :2 Killing Xvnc process ID 17434 cloc3@wlan0 ~ $ vncserver -kill :1 Killing Xvnc process ID 17414 Reproducible: Always Steps to Reproduce: Expected Results: desktop number should correspond to command line input. Instead only the /tmp/.X#-lock file seems corresponding it happens both on tigthvnc-1.2.9-r4 and tigthvnc-1.3*
emerge --info, please
Created attachment 116260 [details] emerge info
it happens on two separated systems. I've attached both emerge--info, even if are very similar.
I've understand the origin of the effect. In my system, I often use tightvnc on localhost. So, I've put `alias vncserver="vncserver -localhost"` in .bashrc. According with `man vncserver` SYNOPSYS, the order of display number and Xvnc options is important in the command. sorry for the bad segnalation.
