touch-packages team mailing list archive

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

Two simple explanations come to mind (need checking):
  * Unity8's check for --desktop_file_hint=... isn't being satisfied in the way the client is launched; or
  * You have packaged a different version libmirclient to that of the libmirserver (we've had some protocol breaks recently).

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

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

** Changed in: mir (Ubuntu)
       Status: New => Incomplete

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

Title:
  Can't init SDL Failed to connect to the Mir Server

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  I build an SDL2 build of dosbox and made a simple click package
  (attached) which fails when run on my bq e4.5:-

  DOSBox version SVN
  Copyright 2002-2015 DOSBox Team, published under GNU GPL.
  ---
  [1447610947.097116] <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"
  Exit to error: Can't init SDL Failed to connect to the Mir Server

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