Nux

Nux draws every single BaseWindow to the backbuffer regardless of what the host WM draw region is

Bug #1091589 reported by Sam Spilsbury
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nux
Fix Released
High
Sam Spilsbury
nux (Ubuntu)
Fix Released
High
Sam Spilsbury

Bug Description

At the moment, this bug is essentially the reason why bug 1091583 exists in unity.

When we switched to using backbuffer persistence in compiz, it means that it was no longer permissible for plugins to draw outside damage boundaries, as that would result in bleeding from the regions beneath not being redrawn. At the moment, calling nux::WindowThread::RenderInterfaceFromForeignCmd causes the entire interface to be drawn on-screen, regardless of the damage region inside of compiz. This means bleeding everywhere.

Nux should support the concept of being able to selectively present its render targets to the screen, so that there's no overdraw when we only need to re-present, eg, the launcher or the panel.

Related branches

Changed in nux:
assignee: nobody → Sam Spilsbury (smspillaz)
status: New → In Progress
Stephen M. Webb (bregma)
Changed in nux:
milestone: none → 4.0.1
Stephen M. Webb (bregma)
Changed in nux:
milestone: 4.0.3 → 4.0.4
Changed in nux:
importance: Undecided → High
Changed in nux (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Sam Spilsbury (smspillaz)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:nux at revision None, scheduled for release in nux, milestone 4.0.4

Changed in nux:
status: In Progress → Fix Committed
Stephen M. Webb (bregma)
Changed in nux (Ubuntu):
status: In Progress → Fix Released
Changed in nux:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.