touch-packages team mailing list archive

[Alan Griffiths <1507982@xxxxxxxxxxxxxxxxxx>]

Comment #16 is misleading:

There is only a "problem" if the app dynamically links against Mir-0.16
and attempts to run against a Mir-0.17 server. This should not happen as
either:

    /1/ the matching server and client libraries are installed as part of the system (desktop, phone); or,
    /2/ the matching server and client libraries are installed as part of a snap (kiosk).

In both cases the client library matches the server and everything
works.

The protocol range checking in r2893 correctly detects that the version
of libmirclient.so.9 that is trying to connect supports that are not
supported by the server and that the system is misconfigured. This is
not something that App developers need to be concerned with.

~~~~

For the avoidance of doubt, Apps built with the libmirclient.so.9 from
Mir-0.17 and installed on a phone configured with Mir-0.16 will
dynamically link and run correctly (case 1 above) unless they refer to
the new functions introduced in 0.17. Vis:

MIR_CLIENT_9v17 {
    mir_blob_from_display_configuration;
    mir_blob_size;
    mir_blob_data;
    mir_blob_release;
    mir_blob_onto_buffer;
    mir_blob_to_display_configuration;
    mir_blob_release;
    mir_buffer_stream_set_scale;
    mir_buffer_stream_set_scale_sync;
    mir_event_get_surface_output_event;
    mir_surface_output_event_get_dpi;
    mir_surface_output_event_get_form_factor;
    mir_surface_output_event_get_scale;
} MIR_CLIENT_9.2;

If the app requires these functions then it obviously can't use a
libmirclient.so.9 from Mir-0.16 and will fail to run even before
connecting to the server.

Similar arguments apply running on a phone configured with or Mir-0.15
or Mir-0.14.

-- 
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/1507982

Title:
  [regression] OTA7 broke previously working app

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Won't Fix
Status in Mir 0.16 series:
  Won't Fix
Status in Mir 0.17 series:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  OTA7 broke previously working app
  after OTA7 update on Meizu MX4, glmark2 stopped working https://uappexplorer.com/app/glmark2.sturmflut
  system updates should not break apps

  
  ~/.cache/upstart$ cat application-click-glmark2.sturmflut_glmark2_0.4.1.log
  libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958)
  Error: Couldn't connect to the Mir display server
  Error: main: Could not initialize canvas
  [1445336019.182277] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in release): /build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958)
  Error: Couldn't connect to the Mir display server
  Error: main: Could not initialize canvas
  [1445336029.784398] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in release): /build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507982/+subscriptions