Rahul, You're using a rather old VNC Server and a non-RFB-compatible viewer. I'd recommend at least upgrading the server to VNC 4.1.1 and trying the screen-saver again.
Cheers, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Rahul > Chawathe (rchawath) > Sent: 27 June 2005 23:37 > To: [email protected] > Subject: RE: Vnc session crashes overnight and dumps core > > Hi > > Nobody seemed to notice the earlier email and/or help. > But anyways for others who may notice such a problem in future, the > cause I figured out for the core dump was due to the screensaver. > Setting kde's option to "no screensaver" doesn't dump core > and crash the > session. > Didn't delve deeper into it. > > > - Rahul > > rahulc AT cisco.com > 408-853-7339 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Rahul Chawathe (rchawath) > Sent: Thursday, June 23, 2005 3:51 PM > To: [email protected] > Subject: Vnc session crashes overnight and dumps core > > Hi > > I started a vnc session on a linux machine running RH7.3, > kernel 2.4.26 > The Xvnc version running on the server side is > 3.3.3r2+tight1.2.2 I use > UltraVnc viewer on the client side, and its release is UltraVnc_RC20 > > I am pretty sure, the server didn't reboot overnight. > But since 2 consecutive mornings, I notice a core dump in my HOME, and > the vnc session has crashed. > > The only process left is > oafd --ac-activate --ior-output-fd=14 > > On doing 'gdb /usr/bin/Xvnc with the core file' > I get the following trace : > > Core was generated by `Xvnc :1 -desktop kde -httpd > /usr/share/vnc/classes -auth /users/rchawath/.Xauth'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib/libnss_nis.so.2 > Reading symbols from /usr/lib/libz.so.1...(no debugging symbols > found)...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from /lib/i686/libm.so.6...(no debugging symbols > found)...done. > Loaded symbols for /lib/i686/libm.so.6 > Reading symbols from /lib/libdl.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /lib/i686/libc.so.6...(no debugging symbols > found)...done. > Loaded symbols for /lib/i686/libc.so.6 > Reading symbols from /lib/libnsl.so.1...(no debugging symbols > found)...done. > Loaded symbols for /lib/libnsl.so.1 > Reading symbols from /lib/libnss_files.so.2...(no debugging symbols > found)...done. > Loaded symbols for /lib/libnss_files.so.2 Reading symbols from > /lib/ld-linux.so.2...(no debugging symbols found)...done. > Loaded symbols for /lib/ld-linux.so.2 > #0 0x08129fc9 in cfb32ClippedLineCopy () > > Has someone experienced this before ? > > thanks, > Rahul > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
