Ubuntu
mir package

  1. Bug #1496069
  2. Comment #14

Comment 14 for bug 1496069

Revision history for this message
Alberto Aguirre (albaguirre) wrote :

So back to the input problem, it's an issue with how we composite with DisplayGroups. We use a single compositor ID, which then makes the RenderingTracker toggle surface visibility on/off.

The RenderingTracker is intended to track if a surface is occluded in all monitors to properly update the surface visibility status. However, since a singe compositor ID is used, the RenderingTracker then incorrectly determines the surface is not visible anywhere after the second composition pass.