← Back to team overview

touch-packages team mailing list archive

[Bug 1507982] Re: OTA7 broke previously working app

 

OK, I have now hacked together a test environment on wily desktop and
tried:

   0.13.3 client --> 0.17.0 server (wily)   FAILS
   0.13.3 client --> 0.16.2 server (lp:mir/0.16)   FAILS
   0.13.3 client --> 0.15.2 server (lp:mir/0.15)   WORKS

I can confirm the primary issue is the first error:

   Error: Couldn't connect to the Mir display server

which is probably the result of:    lp:~alan-griffiths/mir/fix-1486496

Interestingly it works with the server built from 0.15.2. I presume
that's just because the "fix" for bug 1486496 is not present. So perhaps
the only hurdle here is the fix for bug 1486496. It seems if you don't
have that, then a 0.13.3 client can connect and works fine.


** Changed in: mir
       Status: New => Triaged

** Changed in: mir (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: mir
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- OTA7 broke previously working app
+ [regression] OTA7 broke previously working app

** Changed in: mir
    Milestone: None => 0.18.0

** Tags added: regression

-- 
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:
  Triaged
Status in mir package in Ubuntu:
  Triaged

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