This bug was fixed in the package mir - 0.21.0+16.04.20160330-0ubuntu1

---------------
mir (0.21.0+16.04.20160330-0ubuntu1) xenial; urgency=medium

  [ Alberto Aguirre ]
  * New upstream release 0.21.0 (https://launchpad.net/mir/+milestone/0.21.0)
    - ABI summary:
      . mirclient ABI unchanged at 9
      . mirserver ABI unchanged at 38
      . mircommon ABI unchanged at 5
      . mirplatform ABI unchanged at 11
      . mirprotobuf ABI unchanged at 3
      . mirplatformgraphics ABI unchaged at 8
      . mirclientplatform ABI bumped to 5
      . mirinputplatform ABI unchanged at 5
    - Enhancements:
      . New display enumeration API
      . Added Android diagnostic tests to assist during porting to
        new devices
      . Added mir_demo_client_camera: a Video4Linux2 client
    - Bugs fixed:
      . Sometimes devices don't suspend - display turns back on
        immediately (LP: #1549701)
      . Mir crashed with exception 'failed to add sync point to command
        buffer' (LP: #1554635)
      . Mouse cursor is unusably slow in Unity 8 with a 1000Hz mouse
        (LP: #1539009)
      . Packaged mir_unit_tests binary is not suitable for general use
        (LP: #1547015)
      . [regression] Mir stops receiving input after a pause/resume
        cycle (LP: #1548989)
      . NBS (--nbuffers=0) causes software clients to crash with
        std::exception::what: Failed to mmap buffer 13, "Permission denied")
        (LP: #1550432)
      . Fullscreen clients freeze when using NBS with multiple monitors
        (LP: #1551536)
      . [ FAILED ] DisplayConfigurationTest.output_position_is_independent_of_
        orientation (LP: #1552065)
      . The server-side use of MIR_SOCKET is confusing (LP: #1290345)
      . [regression] FTBFS with -DMIR_LINK_TIME_OPTIMIZATION=on
        -Duse_debflags=on (LP: #1350343)
      . Mir On X (mesa-x11) keeps receiving mouse movement events even
        when not focused (LP: #1528110)
      . x11 platform: mouse cursor moves strange (LP: #1546324)
      . Cross compiling to wily/vivid doesn't work (LP: #1549152)
      . Rendering stutters when a new client establishes a connection
        (LP: #1549359)
      . 'mir_demo_server --test-client' crashes (SIGSEGV) when client
        dies (LP: #1555620)
      . [testfail] CI failure: TestClientInput.client_input_config_request_
        receives_all_attached_devices (LP: #1555708)
      . [regression] Mir FTBFS when MIR_ENABLE_TESTS=no (LP: #1556080)
      . Mir-on-X11 doesn't exit (until it gets an event) (LP: #1556210)
      . InputPlatformProbe.x11_platform_found_and_used_when_display_connection_
        works breaks with old input drivers present (LP: #1543049)
      . [regression] MIR_CLIENT_PERF_REPORT is missing window/surface
        names (LP: #1546933)
      . Installed binaries fail to run with mir_demo_server --test-client XXXX
        (LP: #1556160)
      . mir_demo_server --test-client [mir_demo_client_scroll|
        mir_demo_client_flicker] fails (LP: #1556205)
      . The contents of debian/mir-demos.examples are out of date and useless
        (LP: #1557446)

  [ CI Train Bot ]
  * No-change rebuild.

 -- Alberto Aguirre <[email protected]>  Wed, 30 Mar 2016
00:23:20 +0000

** 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/1543049

Title:
  InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works
  breaks with old input drivers present

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When there is a bump in the graphics platform ABI but no simultaneous
  bump in the input side we end up having more usable X11 platforms than
  expected. Because of the bump we get two x11 server modules:

  $ ls lib/server-modules/
  graphics-android.so.7  graphics-dummy.so       graphics-mesa-kms.so.8  
input-evdev.so.4  input-stub.so         server-mesa-x11.so.8
  graphics-android.so.8  graphics-mesa-kms.so.7  graphics-throw.so       
input-evdev.so.5  server-mesa-x11.so.7

  And as the log shows both are supported as input platforms (but only
  one would work as a graphics platform):

  $ bin/mir_unit_tests --gtest_filter=InputPlatformProbe*
  MIR_CLIENT_PLATFORM_PATH=bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=bin/../lib/server-modules/
  LD_LIBRARY_PATH=bin/../lib
  exec=bin/mir_unit_tests.bin
  Running main() from main.cpp
  Note: Google Test filter = InputPlatformProbe*
  [==========] Running 4 tests from 1 test case.
  [----------] Global test environment set-up.
  [----------] 4 tests from InputPlatformProbe
  [ RUN      ] InputPlatformProbe.stub_platform_not_picked_up_by_default
  [2016-02-08 10:25:31.446023] mirserver: Selected input driver: 
mir:evdev-input (version: 0.20.0)
  [       OK ] InputPlatformProbe.stub_platform_not_picked_up_by_default (34 ms)
  [ RUN      ] 
InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works
  [2016-02-08 10:25:31.460373] mirserver: Selected input driver: mir:x11-input 
(version: 0.20.0)
  [2016-02-08 10:25:31.462505] mirserver: Selected input driver: x11-input 
(version: 0.19.0)
  [2016-02-08 10:25:31.488286] mirserver: Selected input driver: 
mir:evdev-input (version: 0.20.0)
  
/home/alan/display_server/development-branch/tests/unit-tests/input/test_input_platform_probing.cpp:149:
 Failure
  Value of: platforms
  Expected: has 2 elements and there exists some permutation of elements such 
that:
   - element #0 is a or derived from a N3mir5input5evdev8PlatformE, and
   - element #1 is a or derived from a N3mir5input1X14XInputPlatformE
    Actual: { 24-byte object <F0-8F 46-04 00-00 00-00 E0-8F 46-04 00-00 00-00 
00-D4 43-04 00-00 00-00>, 24-byte object <60-94 46-04 00-00 00-00 50-94 46-04 
00-00 00-00 80-DA 43-04 00-00 00-00>, 24-byte object <A0-D5 43-04 00-00 00-00 
90-D5 43-04 00-00 00-00 50-DA 45-04 00-00 00-00> }, which has 3 elements
  [  FAILED  ] 
InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works 
(42 ms)
  [ RUN      ] InputPlatformProbe.x11_input_platform_not_used_when_vt_specified
  [2016-02-08 10:25:31.524523] mirserver: Selected input driver: 
mir:evdev-input (version: 0.20.0)
  [       OK ] InputPlatformProbe.x11_input_platform_not_used_when_vt_specified 
(36 ms)
  [ RUN      ] InputPlatformProbe.allows_forcing_stub_input_platform
  [2016-02-08 10:25:31.530326] mirserver: Selected input driver: mir:stub-input 
(version: 0.20.0)
  [       OK ] InputPlatformProbe.allows_forcing_stub_input_platform (5 ms)
  [----------] 4 tests from InputPlatformProbe (117 ms total)

  [----------] Global test environment tear-down
  [==========] 4 tests from 1 test case ran. (118 ms total)
  [  PASSED  ] 3 tests.
  [  FAILED  ] 1 test, listed below:
  [  FAILED  ] 
InputPlatformProbe.x11_platform_found_and_used_when_display_connection_works

   1 FAILED TEST

  If we have a release with a bump like this, users upgrading might end
  up in a problematic configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1543049/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to