Comment 8 for bug 39046

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.