** Changed in: compiz-core
Status: Incomplete => Fix Released
** Changed in: compiz
Status: Incomplete => Fix Released
** No longer affects: compiz-core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: compiz
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762264
Title:
Dual-head initial render of left screen is wrong after login
To manage
Hi, Bryce. Can you still reproduce this issue on 11.10/12.04? Thanks.
** Also affects: compiz-core
Importance: Undecided
Status: New
** Changed in: compiz-core
Status: New = Incomplete
** Changed in: compiz (Ubuntu)
Status: New = Incomplete
--
You received this bug
In fact just upgraded this box Friday. The issue is gone in both
oneiric and precise.
** Changed in: compiz (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762264
Title:
Dual-head initial render of left screen is wrong after login
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: Photo showing incorrect rendering on left screen
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/762264/+attachment/2044203/+files/100_2038.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note how the remainder of the window on the left monitor does not show
on the right.
** Attachment added: Closeup showing the issue
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/762264/+attachment/2044205/+files/100_2039.JPG
--
You received this bug notification because you are a
One click on the titlebar of a window on the left screen is sufficient
to restore the rendering.
I gather the click triggers a redraw event.
I can try booting a few different ways to isolate it if you'd like. But
I'm guessing this may already be a known issue, so will wait until
someone has
