VNC Stopped Working After Installing Solaris 9 Recommended Patches

[Steve Waltner]

I found the solution. I needed to backout the following patches.

112807-18
112661-11
112785-58

The first two depend upon the last one, which was the culprit. Patch  
112785-58 includes a broken X font server, which would crash. inetd  
would occasionally kill the fs.auto service and then 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 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 to my Xvnc process...
>
> ra:~> /usr/ucb/ps auxwwwwww | grep Xvnc | grep swaltner
> swaltner 22928  0.1  0.1 8152 6784 pts/27   S 11:24:45  0:00 Xvnc : 
> 14 -desktop ra:14 (swaltner) -httpd /soft/cfr/vnc/4.1.2/java -auth / 
> home/swaltner/.Xauthority -geometry 1024x850 -depth 16 -rfbwait  
> 30000 -rfbauth /home/swaltner/.vnc/passwd -rfbport 5914 -pn - 
> IdleTimeout=0 -fp /usr/openwin/lib/X11/fonts/misc/,/usr/openwin/lib/ 
> X11/fonts/75dpi/
> swaltner   148  0.0  0.0 1048  840 pts/27   S 11:40:04  0:00 grep Xvnc
> ra:~>
>
> When I try to send X11 graphics to that Xvnc process, I get BadAtom  
> errors.
>
> ra:~> xterm -display ra:14
> Warning: Actions not found: string, scroll-back, scroll-forw
> xterm:  unable to open font "8x10", trying "fixed"....
> X Error of failed request:  BadAtom (invalid Atom parameter)
>   Major opcode of failed request:  20 (X_GetProperty)
>   Atom id in failed request:  0x0
>   Serial number of failed request:  90
>   Current serial number in output stream:  90
> ra:~>
>
> Out of the 157 patches in the patch bundle, each system had  
> anywhere from 85-125 patches that were installed/updated, several  
> of these were related to X.
>
> The problems seem to come and go, which is the really annoying  
> thing. This was working perfectly when I went home at midnight last  
> night, but failed at 8:00. Many users report that trying to start  
> the VNC session a couple times eventually starts a session.
>
> I've got backup copies of my VNC server log files from before the  
> upgrade, and while there are several warning/error messages in it,  
> except for timestamps, they are exactly the same.
>
> Any suggestions on where to look?
>
> Steve
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list