You might try using a ~/.vnc/xstartup file that looks more like...
==
#!/bin/sh
[ -r \$HOME/.Xresources ] && xrdb $HOME/.Xresources
# Start clipboard helper app
vncconfig -nowin &
/usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
display=`echo $DISPLAY | sed -e 's/.*:/:/'`
restart it after
a pause, which was why the problem would come and go.
As to why this was making Xvnc return BadAtom errors, who knows
Steve
On Mar 1, 2007, at 11:53 AM, Steve Waltner wrote:
I'm running the free distribution of RealVNC 4.1.2. I installed the
Solaris 9 Recommended patch b
I'm running the free distribution of RealVNC 4.1.2. I installed the
Solaris 9 Recommended patch bundle I downloaded on Feb 21, 2007 onto
my Solaris 9 systems last night. This was primarily done to get the
updates for the DST changes. Now, we're having trouble using VNC.
Here's the arguments
I've seen a similar issue on our Solaris 9 systems, but I rarely saw
the memory size go above 500 MB. We had been running VNC 3.3.3r2 from
AT&T until very recently when I switched that out with RealVNC (Free)
4.1.2. This upgrade was being done to fix two problems, one of which
was the memor