Basil Copeland wrote:
More:
I changed the session for root to :2. That boots up and starts vncserver with no errors (and I can log in remotely just fine).
This being a new installation, I have only one other account. I seem to recall initially trying to set up vncserver for this account, though there was no .vnc directory in this users home account. Anyway, I ran vncserver for this account, and it responded as if this were the first time it was run, and assigned it session :1. I added this to /etc/sysconfig/vncservers. The system continues to start Xvnc successfully at startup, but it only returns a successful start for :2, not :1, and I cannot remote in on :1.
I can work with this, as I have it working on :2, and can probably set up additional sessions.
But I hate unsolved mysteries, especially when it comes to my computers. So I wish I could figure out what is wrong with vnc on :1.
--- Basil Copeland <blcjr@xxxxxxxxx> wrote:
--- Joshua Andrews <josh@xxxxxxxxxxxx> wrote:
Sounds like an old lock on :1. Have you tried `vncserver -kill :1`
Yes, I've tried that. Doesn't work. Remember, even though vncserver doesn't start during startup -- it fails with the error message saying that it is already running on :1 -- when I run vncserver from a command prompt on logging in, it starts up on :1! (Of course, the "-kill :1" works then. There's something bogus, or very odd, going on to produce that error message during startup, because I can find no evidence of Xvnc running until I run vncserver from the command prompt after startup.)
Thanks, though, for the reply.
Have you looked in /tmp/X11-unix/=X1? -- for and old socket?
