We have a production machine running Suse 11 Enterprise Server x86_x64 with tigtvnc as the VNC server used to connect remotely via UltraVNC view on a Windows 7 machine. Up to this point, the setup has worked wonderfully. This machine is one of lesser accessed machines by one of my coworkers that prefers a GUI administration. With that said, I am not sure when the problem started or what might have caused it.
The first sign of the problem that was noticed was when trying to launch Konqueror. It acts like it tries to start (as evident in the task bar) for a moment, then disappears and nothing ever launches. The other problem is that when you go to add a widget, then entire X session greys out with the only option to end the VNC session.
The real problem is when I try to kill the session via putty I get:
server:/ # vncserver -kill :1 Cant't find file /root/.vnc/server:1.pid You'll have to kill Xvnc process manually
And when I try to start it:
server:/ # vnserver :1 A VNC server is already running as :1
Also tried this:
server:/ # /sbin/service vncserver stop service: no such service vncserver
ps -A doesn't reveal anything VNC related (Xvnc, vncserver, etc. I'll post the process list if requested)
What gives? How do I kill this thing? Since it's on a production machine, any restart request is a big bureaucratic process, so I am trying to avoid that as well.