krfb crashes when a connected client move mouse

i forgot to tell that my krfb server is configure to accept non invit connection to control desktop.

after more tests it never appear when client is krdc (invite or non-invite connection) only when i use realvnc client.

I've had this problem as well, but it's inconsistent. It sometimes (not always) works as long as the client is set to true color, but never works otherwise.

See backtrace in https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/103706

For what it's worth - the same thing happens with UltraVNC viewer on WinXP SP2, connecting to all versions I tried of Kubuntu (Dapper/Edgy/Feisty). Completely unusable.

This indeed sounds like kde-bugs #124529, however as they say, it's resolved in KDE 4.0 and cannot be easily fixed in previous versions. So perhaps the Kubuntu bug should be changed to a request to replace Krdc with some other default VNC server that isn't so significantly broken (with many different viewers, as is evident from that bug report), at least until KDE 4 is introduced to Kubuntu.

In the meanwhile, what's the recommended alternative VNC server to install in place of Krdc?

fixed in kde4, therefore marking as fix committed.

Upstream is not going to fix this in kde3, as the codebase has changed so much.

Sarah,

I'm not sure that is a viable solution. As far as I know KDE4 is not going to be part of Gusty. This would leave Kubuntu users without an integrated vnc for probably a year. More over, the option is in their menu where it looks like it would work.

As a developer, I understand the difficulty to backport fixes when a major code changes have happened. If Kubuntu is going to continue to support KDE3, then an interim option should be supported. Not doing so leaves Kubuntu users with a bad taste in their mouth when they try to get it work over and over again. Also, this keeps bug #1 from not being closed.

I believe I have a viable solution for anyone effected by this bug. Anyone with some familiarity with the command line should be able to accomplish this.

 * Install x11vnc:

sudo apt-get install x11vnc

 * Create a vncpassword if you haven't already:

mkdir ~/.vnc
 x11vnc -storepasswd ~/.vnc/passwd

* Create your config file in ~/.x11vncrc to look something like this:

forever
localhost
rfbauth /home/<USERNAME>/.vnc/passwd
display :0
#You can use rfbport to specify a different port (default is 5900).
#Remove localhost if you plan on connecting from a second computer

* Create a file "~/.kde/Autostart/x11vnc" with the following contents:
#!/bin/bash
/usr/bin/x11vnc &

* Set the executable permissions on the autostart file:
chmod +x ~/.kde/Autostart/x11vnc

At this point you need to log out of KDE and back in to test your setup. I use SSH with port forwarding to establish my remote connections. That topic is beyond the scope of this document though. If you do not use port forwarding you will need to remove the "localhost" line from your .x11vncrc file.

This information was scraped up from the a few sources. Namely the x11vnc man page and the following webpage:
http://gentoo-wiki.com/HOWTO_Use_VNC_to_connect_to_existing_X_Sessions

Someone should put this on Ubuntu's Wiki if they haven't already.

Sorry if there are any typos above. Feel free to comment any corrections.

Mike,

KDE4 RC2 will be in universe, as long as it all stays on time.

And, as always, patches welcome :)

Just checked to see if the upstream fix made it into the 3.5.9 release and it has. I just tested this and the issues seems to be resolved. Thanks!