touch-packages team mailing list archive

[Launchpad Bug Tracker <1499042@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package mir - 0.17.0+15.10.20151008.2-0ubuntu1

---------------
mir (0.17.0+15.10.20151008.2-0ubuntu1) wily; urgency=medium

  [ Alexandros Frantzis ]
  * New upstream release 0.17.0 (https://launchpad.net/mir/+milestone/0.17.0)
    - ABI summary: Only servers and graphics drivers need rebuilding;
      . Mirclient ABI unchanged at 9
      . Mirserver ABI bumped to 35
      . Mircommon ABI unchanged at 5
      . Mirplatform ABI bumped to 11
      . Mirprotobuf ABI bumped to 3
      . Mirplatformgraphics ABI bumped to 6
      . Mirclientplatform ABI unchanged at 3
    - Enhancements:
      . Introduce libmircookie, a simple mechanism for a group of cooperating
        processes to hand out and verify difficult-to-forge timestamps to
        untrusted 3rd parties.
      . More refactorings to support renderers other than GL.
      . Add MirBlob to the client API - a tool for serializing and
        deserializing data.
      . Introduce a libinput based input platform, not yet used by default.
      . Provide a mechanism for the shell to send events on surface
        construction.
      . Provide mir::shell::DisplayConfigurationController allowing shells
        to correctly change the display configuration, notifying clients
        as appropriate.
      . New DSO versioning guide.
      . Send events pertaining to the output a surface is currently on (dpi,
        form factor, scale) to clients.
    - Bug fixes:
      . [enhancement] XMir specific documentation should live in its own
        subsection (LP: #1200114)
      . Nested servers need cursor support (LP: #1289072)
      . Mir cursor is missing/invisible until the client sets it multiple
        times (LP: #1308133)
      . [regression] Fullscreen software surfaces (like Xmir -sw) can crash
        the Mir server (LP: #1493721)
      . [usc] Mir gives up and shuts down due to input with multimonitor qtmir
        (std::exception::what: Failure sending input event) (LP: #1496069)
      . Mouse cursor disappears upon entering the surface area of a nested
        client (LP: #1496849)
      . [android] input is not dispatched when attaching an external monitor
        (LP: #1498045)
      . [android] input coordinates are scaled incorrectly when an external
        display is connected (LP: #1498540)
      . [android] std::exception::what: error during hwc set() when unplugging
        external monitor (LP: #1498550)
      . tests do not compile without precompiled headers (LP: #1498829)
      . [android] std::exception::what: Failed to monitor fd: Operation not
        permitted when unplugging external display in a nested configuration
        (LP: #1499042)
      . Mir suddenly no longer builds since 'mesa (11.0.0-1ubuntu1) wily':
        /usr/include/EGL/eglplatform.h:100:35: fatal error:
        android/native_window.h: No such file or directory (LP: #1499134)
      . [android] various crashes when unplugging external display on a
        nested configuration (LP: #1501927)
      . Cursor becomes visible by itself when an external monitor is connected
        (LP: #1502200)
      . mesa FTBFS due to missing Requires in mirclient (LP: #1503450)

  [ CI Train Bot ]
  * New rebuild forced.

 -- Alexandros Frantzis <alexandros.frantzis@xxxxxxxxxxxxx>  Thu, 08 Oct
2015 16:12:19 +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/1499042

Title:
  [android] std::exception::what: Failed to monitor fd: Operation not
  permitted when unplugging external display in a nested configuration

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

Bug description:
  Using the following nested configuration:

  sudo mir_demo_server --arw-file --display-config=sidebyside --input-
  report log --legacy-input-report log --scene-report log --debug
  --window-manager system-compositor --hwc-report log

   mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir
  --display-config sidebyside --input-report log --legacy-input-report
  log --scene-report log --debug

  mir_demo_client_fingerpaint -m /tmp/nested_mir

  The nested server occasionally crashes. Excerpt of the last lines in
  the log:

  Input channel destroyed: name='Mir Fingerpaint', fd=34
  [1443033760.712569] scene: surface_removed(0xb2601908 ["Mir Fingerpaint"]) - INFO surface count=2
  Input channel destroyed: name='decoration', fd=38
  [1443033760.712935] scene: surface_removed(0xb2602eb8 ["decoration"]) - INFO surface count=2
  [1443033760.713057] scene: surface_deleted(0xb2601908 ["Mir Fingerpaint"]) - INFO surface count=1

  [1443033760.721541] scene: surface_deleted(0xb2602eb8 ["decoration"])
  - INFO surface count=0

  ERROR: /build/mir-GYyRoo/mir-0.15.1+15.04.20150903/src/common/dispatch/multiplexing_dispatchable.cpp(263): Throw in function void mir::dispatch::MultiplexingDispatchable::add_watch(const std::shared_ptr<mir::dispatch::Dispatchable>&, mir::dispatch::DispatchReentrancy)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt12system_errorEEEE
  std::exception::what: Failed to monitor fd: Operation not permitted

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