Date: Mon, 23 Jun 2003 20:59:34 -0500 From: Rik Scarborough <RikSca@kc.rr.com> To: Charlie Schluting <charlie@schluting.com> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: KDE VNC server crashes Message-ID: <20030624015934.GA1104@gruffy.kc.rr.com> In-Reply-To: <3EF7AE73.1010405@schluting.com> References: <20030624004725.GA823@gruffy.kc.rr.com> <3EF7AE73.1010405@schluting.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Jun 2003, Charlie Schluting wrote: > Rik Scarborough wrote: > >I'm having a problem with KDE's VNC server under FreeBSD. > > > >I can connect to one machine that is running KDE and set to allow > >uninvited guests, but when I disconnect from that machine the VNC server > >(krfb) crashes with the following message. > > The Application unknown (krfb) crashed and caused the signal 11 > > (SIGSEGV). > > My guesses: > 1. Bad memory? Hmm, I may try on another computer to see if I get the same results. > 2. VNC sucks. Try tightVNC, I've had the best luck with that. Sometimes > on some computers I have to muck with the compression setting.. but for > the most part it works well. Come to think of it, VNC doesn't really > suck, but its pretty hard on bad hardware ;) (I seem to remember the > NIC on that box was found to be flakey). It's not VNC itself, this is KDE's implementation of the VNC protocol (although they may share code). I can't go to tightVNC, because I need to control the :0.0 screen. VNC and tightVNC just create new screens. ~Rik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030624015934.GA1104>