touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Hi dinamic, good to hear from you again.

We do know of a protocol compatibility break that occurred in Mir
0.15.0, which was first reported as bug 1486496 (which due to
disagreements got reworded and watered down such that mir-team was not
required to fix the regression). I also mentioned back in August that it
could become a problem for Snappy:
https://bugs.launchpad.net/mir/+bug/1486496/comments/15

Although I was trying for protocol backward-compatibility at the time,
that's not something we can realistically maintain forever. And it was
rightly pointed out that in a traditional packaging system the problem
mostly would not exist as even old clients would start using the new
(shared!) libmirclient/libmirprotobuf automatically.

So this really is mostly just an issue we'll see in Snappy where apps
carry their own libmir* client libraries. Here are some possible ways
forward for us:

  (a) App developers: Maybe ensure apps don't package libmir* and instead rely on that of the system/mir framework already installed; or
  (b) ~mir-team: make a conscious decision to maintain socket protocol level compatibility for the lifetime of the given Ubuntu Touch series (which unfortunately also means supporting old buffer semantics too). Kind of analogous to what people usually do with ABIs; or
  (c) ~mir-team: As we know the precise point of regression (r2730), make an effort to reinstate protocol backward compatibility (although this suggestion was met with strong opposition previously, and admittedly would be difficult to maintain forever).

Options (a) and (b) are most likely and unfortunately both require your
app packages to get rebuilt/re-released. Maybe there are more options?

** Also affects: mir
   Importance: Undecided
       Status: New

-- 
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:
  OTA7 broke previously working app

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New

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