I experienced another nasty bug with vino server and Ubuntu 10.10 (some reports the same thing on other Distros, even on older versions of Ubuntu): After authenticating on VNC, the client windows is not updated.
All the events are sent by mouse correctly on the desktop (you can see the mouse moving and reacting at left/right click), but the VNC client window is not updated, in other words I see only the first image what I get it when I connected first time.
I found a workaround for this problem: uninstall compiz and everything will be all right. I believe this is a bug in vino-server and should be fixed on the next updates, but until then, removing the compiz is the best workaround. The bug is already reported here.
Good Luck!
Long time, no see 
I installed the alpha version of Ubuntu 10.10 and I had a small problem: VNC Server (vino-server) doesn’t start. If you take a look on your home folder, in file .xsession-errors probably you will find:
13/10/2010 07:47:39 PM Autoprobing TCP port in (all) network interface
13/10/2010 07:47:39 PM Listening IPv6://[::]:5900
13/10/2010 07:47:39 PM Listening IPv4://0.0.0.0:5900
13/10/2010 07:47:39 PM Autoprobing selected port 5900
13/10/2010 07:47:39 PM Advertising security type: 'TLS' (18)
13/10/2010 07:47:39 PM Advertising authentication type: 'VNC Authentication' (2)
13/10/2010 07:47:39 PM Advertising security type: 'VNC Authentication' (2)
** Message: Received signal 11, exiting...
I read a lot of solutions from internet about how to fix that and I will try to describe them here:
First, was the reinstall:
$ sudo aptitude reinstall vino-server
But doesn’t work for me.
Second, was to replace vino-server binary from /usr/lib/vino with the binary from Ubuntu 10.4, that worked, but I wasn’t totally satisfied (what it will happen at next upgrade ?)
After I study a little bit, the bug from Ubuntu launchpad, I found the best solution for me:
I disabled uPNP from my router. Yes, it is so simple. On my Linksys router I found uPNP under Administration -> Management.
So, no changes on my workstation and VNC works great.
Good Luck!
Sometimes you need standby for your Xorg server and sometimes not (surveillance applications don’t need it). I will try to show you in several lines how you can configure that.
To control standby for your monitor you need to see if you have enabled Display Power Management Signaling enabled.
For that try to run following command in a xterm
$xset q
DPMS (Energy Star):
Standby: 1200 Suspend: 1800 Off: 2400
DPMS is Enabled
Monitor is On
if is not enabled just run
$xset +dpms
To set standby, suspend and off parameters run
$xset dpms X Y Z
where X is standby time, Y is suspend time and Z is off time all in seconds.
To set that at every Xorg boot then you should add the following lines to your xorg.conf
Section “ServerFlags”
Option “blank time” “150″
Option “standby time” “300″
Option “suspend time” “600″
Option “off time” “1200″
Option “dpms” “true”
EndSection
If you want to disable DPMS standby then put this configuration in your xorg.conf
Section “ServerFlags”
Option “blank time” “0″
Option “standby time” “0″
Option “suspend time” “0″
Option “off time” “0″
Option “dpms” “false”
EndSection
Also read here http://www.randombugs.com/linux/disable-monitor-standby-xorg-xserver.html
If you copy your shortcuts from one system to another and you don’t preserve the right attributes on this files then is possible to get a warning everytime when you run a application from your desktop or your menus.
This shortcut should be a *.desktop file and it should have your rights on it or it should have minimum read and execute for group or others.
to fix that just run
sudo chmod ugo+rx *.desktop
That means you give rx rights (read and execute) to ugo (user, group and other).
So now, you also learned how to set the proper file rights
I know you can also use mark as trusted button, but is very useful when you have more than 40 shortcuts on your desktop.
