This bug was fixed in the package mir - 0.11.0+15.04.20150209.1-0ubuntu1
---
mir (0.11.0+15.04.20150209.1-0ubuntu1) vivid; urgency=medium
[ Daniel van Vugt ]
* New upstream release 0.11.0 (https://launchpad.net/mir/+milestone/0.11.0)
- Enhancements:
. Lots more major plumbing in the Android code, on the path to
supporting external displays.
. Add support for clang 3.6.
. Major redesign of server classes in mir::shell,scene and friends
(still in progress).
. Added client API for creating dialogs and tooltips.
. Added new surface states: mir_surface_state_hidden and
mir_surface_state_horizmaximized.
. Performance: Use optimally efficient fragment shading when possible.
. Performance: (Desktop) Composite using double buffering instead of
triple to reduce visible lag.
. mir_proving_server: Can now resize windows from any edge or corner
using the existing Alt+middlebuttondrag.
. mir_proving_server: Added some demo custom shaders (negative and
high contrast modes: Super+N/C).
. mir_proving_server: Can now close clients politely via Alt+F4.
. Added MirPointerInputEvent (part of the new input API, the old
MirMotionEvent is still supported also for now).
- ABI summary: Servers need rebuilding, but clients do not;
. Mirclient ABI unchanged at 8
. Mircommon ABI unchanged at 3
. Mirplatform ABI bumped to 6
. Mirserver ABI bumped to 29
- Bug fixes:
. [regression] mir_demo_server exits immediately with boost
bad_any_cast exception (LP: #1414630)
. need way to position menus and tooltips (relative positioning to
parent) (LP: #1324101)
. GLibMainLoopTest failure seen in CI (LP: #1413748)
. Clang builds fail in CI (LP: #1416317)
. segfault in mir::compositor::GLProgramFamily::Shader::init()
(LP: #1416482)
. GLRenderer: The default fragment shader is sub-optimal for alpha=1.0
(LP: #1350674)
. mesa::DisplayBuffer::post_update is triple buffered - more laggy than
it needs to be (LP: #1350725)
. Cannot connect to nested server when started from a differen vt
(LP: #1379266)
. [testfail] AsioMainLoopAlarmTest fails in CI (LP: #1392256)
. Compositor report inconsistently reports frame time during bypass,
and render time otherwise (LP: #1408906)
. [regression] mir_demo_client_fingerpaint doesn't paint anything any
more (with the mouse) (LP: #1413139)
. Hardware cursor is always slightly ahead of the composited image
(LP: #1274408)
. integration tests are outputting (too many) DisplayServer log
messages (LP: #1408231)
. [regression] deploy-and-test.sh doesn't work any more (unless you
have umockdev installed already) (LP: #1413479)
. Color Inverse on display. Toggle Negative Image (LP: #1400580)
. mir-ubuntu-vivid-armhf-ci fails consistently (LP: #1407863)
. Double-buffered surfaces may lag or freeze if event driven and not
constantly redrawing (LP: #1395581)
. Pointer motion and crossing events are missing (LP: #1417650)
-- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 09 Feb 2015
21:27:35 +
** Changed in: mir (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1408906
Title:
Compositor report inconsistently reports frame time during bypass, and
render time otherwise
Status in Mir:
Fix Committed
Status in mir package in Ubuntu:
Fix Released
Bug description:
Compositor report inconsistently reports frame time during bypass, and
render time otherwise. As of Mir 0.10.0 on mesa it should be reporting
render time exclusively (i.e. zero for bypass). Not the frame time.
[1420787439.536901] (II) compositor: Display 0x7fcd6c000920 averaged 59.898
FPS, 0.363 ms/frame, latency 15.728 ms, 60 frames over 1.001 sec, 0% bypassed
[1420787440.538606] (II) compositor: Display 0x7fcd6c000920 averaged 59.897
FPS, 0.404 ms/frame, latency 15.625 ms, 60 frames over 1.001 sec, 0% bypassed
[1420787442.569138] (II) compositor: Display 0x7fcd6c000920 averaged 22.161
FPS, 0.442 ms/frame, latency 15.153 ms, 45 frames over 2.030 sec, 0% bypassed
[1420787442.608043] (II) compositor: Display 0x7fcd6c000920 bypass ON
[1420787443.576615] (II) compositor: Display 0x7fcd6c000920 averaged 59.555
FPS, 16.375 ms/frame, latency 15.763 ms, 60 frames over 1.007 sec, 98% bypassed
[1420787444.578286] (II) compositor: Display 0x7fcd6c000920 averaged 59.899
FPS, 16.652 ms/frame, latency 16.100 ms, 60 frames over 1.001 sec, 100% bypassed
[1420787445.580003] (II) compositor: Display 0x7fcd6c000920 averaged 59.897
FPS, 16.653 ms/frame, latency 16.115 ms, 60 frames over 1.001 sec, 100%
