2012-04-29

VNC服务器在开启compiz时不工作 | VNC server won't work with compiz

症状是VNC远程连接后,画面显示一帧就不再刷新了
(但是鼠标键盘在本机好像是有响应的)

以前讨论过这个问题
http://coolwanglu.blogspot.com/2011/01/compizfglrxvnc-problem-of-vnc-server.html

今天再次遇到了,只是现在我的电脑是ATI的卡
vino不太好用,用x11vnc的时候出现消息

29/04/2012 21:14:17 XDAMAGE is not working well... misses: 166/216
29/04/2012 21:14:17 Maybe an OpenGL app like Beryl or Compiz is the problem?
29/04/2012 21:14:17 Use x11vnc -noxdamage or disable the Beryl/Compiz app.
29/04/2012 21:14:17 To disable this check and warning specify -xdamage twice.

用 x11vnc -noxdamage -once -display :0 可以正常使用,但是由于不是增量显示的,网络压力会很大


https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/772873
看到一个 workaround
是说在ATI Catalyst Control Center (Administrative)里打开 tear free 这个选项

我试了一下,果然管用。
以后不用-noxdamage也能正常使用了

另外-once这个选项太好用了


 The symptom is after a successful vnc connection, the window stopped refreshing after the first frame.
(But the keyboard and mouse seems to be responded on the remote machine)

I've discussed about the problem before:
http://coolwanglu.blogspot.com/2011/01/compizfglrxvnc-problem-of-vnc-server.html

Today I encountered this problem again when I tried to connect to my machine, but now I'm using an ATI graphics card.
vino server is not quite handy, so I used x11vnc, and I saw some useful logs:


29/04/2012 21:14:17 XDAMAGE is not working well... misses: 166/216
29/04/2012 21:14:17 Maybe an OpenGL app like Beryl or Compiz is the problem?
29/04/2012 21:14:17 Use x11vnc -noxdamage or disable the Beryl/Compiz app.
29/04/2012 21:14:17 To disable this check and warning specify -xdamage twice.

I can access my machine with 'x11vnc -noxdamage -once -display :0' without any problem, but now the screen is no longer updated incrementally, so it would hammer the network.

Then I found a workaround at:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/772873

It says to enable the 'tear free' option in the ATI Catalyst Control Center (Administrative)

I tried, and it really worked!
Then it still works without the '-noxdamage' option

BTW, I really like the '-once' option.



No comments: