for trouble shooting, i have some updates. all are personal opinions and
welcome to point out my misunderstanding.
based on fglrx driver.
when using metacity, we can see ProcCopyArea is frequently invoked if i drag a
window around desktop. it help to update the damage region to some drawable
which is indicated by VINO as following:
vfb->priv->xdamage = XDamageCreate (vfb->priv->xdisplay,
GDK_WINDOW_XID (vfb->priv->root_window),
XDamageReportDeltaRectangles);
in fact, the drawable ID is 186 on my platform, and i can oberve that
DamageExtNotify for that ID in this case. the codestack shows it is triggered
by damageCopyArea which is mentioned above. then VINO works well. key point,
this copy is absolutely not requested by VINO because the client ID is
different, so it's not the copy between RFB and root window. i wonder if it is
metacity doing this copy.
while, change to compiz. ProcCopyArea won't be invoked for draging a
window. no damage updates to drawable 186. VINO freezes.
actually we can force to flush some damages to drawable monitored by
VINO, that's why enabled tear free option gives us a workaround,
rotating screen also helps. but i don't prefer to add this flushing into
common cases.
i also got some questions:
how does compiz draw the window while it is moving? if it won't copy area, is
there any method to get the damages in Xserver side? i suppose it uses OGL to
directly draw this process, but m not sure where it is rendered, root window or
redirect window? i ask OGL guys to report kinds of damage to fglrx driver, no
effect.
i carefully say that it might be issue of DRI in fglrx driver, because
radeon driver supports VINO much better, and DRI in fglrx doesn't comply
with standards quite well. so all my info and questions are for the
purpose of fixing this issue. if any buddy know the damage reporting
mechanism for drawable monitored by VINO in COMPIZ+RADEON case, please
help me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/772873
Title:
Vino does not work with compositing
Status in “fglrx-installer” package in Ubuntu:
Triaged
Status in “fglrx-installer” source package in Natty:
Won't Fix
Status in “fglrx-installer” source package in Oneiric:
Won't Fix
Status in “fglrx-installer” source package in Precise:
Triaged
Bug description:
Binary package hint: vino
Vino, the built in VNC server in Ubuntu, has had a problem for many
releases where it won't update the display when connected remotely if
compositing is enabled.
I honestly don't know why it was shipped with this version since
compositing is now required and enabled by default, but Vino doesn't
work if compositing is enabled.
After upgrading to Natty there is no user-facing way to disable
compositing, so the built-in remote control application is now
completely useless.
This is a core functionality of a desktop operating system and it has
been broken in Ubuntu for several major releases ( see bug 353126
which was opened on 2009-4-1).
If if it's not a core functionality to everyone and that's just my
opinion, it doesn't make any sense to ship a desktop OS with a broken
remote control service. I don't know of any other desktop OS that
ships with a remote desktop functionality that is completely broken
out of the box.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: vino 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Apr 28 19:28:50 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: vino
UpgradeStatus: Upgraded to natty on 2011-04-29 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/772873/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
